There is no support for multi-key credential secret in ProviderConfigSpec

[muvaf]

What problem are you facing?

Alibaba Provider uses two pre-defined keys in their credentials secret. However, ProviderConfigSpec source type Secret assumes that all credentials should exist in under one key and that key is required. So, right now we have to give a dummy key value so that it passes api-server validation.

How could Crossplane help solve your problem?

• Add multi key support for Secret credentials source.
• Add another credentials source like MultikeySecret.
• Alibaba Provider could implement its own ProviderConfigSpec with stuff necessary to work with PCU.
• Alibaba Provider could invent a format for a single cred blob and use it, something similar to AWS CLI cred format.

I feel like third option is the way to go right now but I do expect this problem to pop up in future providers.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.