We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any hints on how the credentials need to be structured to make this provider work?
I found this https://github.com/crossplane-contrib/provider-confluent/blob/main/cluster/test/setup.sh#L6 but its a bit of a guessing game what is contained in : "${UPTEST_CLOUD_CREDENTIALS}"
The text was updated successfully, but these errors were encountered:
worked it out:
kubectl -n crossplane create secret generic provider-confluent-secret --from-literal=credentials='{"cloud_api_key":"$API_KEY", "cloud_api_secret":"$API_SECRET"}' --dry-run=client -o yaml
Sorry, something went wrong.
worked it out: kubectl -n crossplane create secret generic provider-confluent-secret --from-literal=credentials='{"cloud_api_key":"$API_KEY", "cloud_api_secret":"$API_SECRET"}' --dry-run=client -o yaml
Yup you got it! :)
kind: Secret metadata: name: confluent-provider-config namespace: crossplane-system data: credentials: '{"cloud_api_key":"$API_KEY", "cloud_api_secret":"$API_SECRET"}'
Successfully merging a pull request may close this issue.
Any hints on how the credentials need to be structured to make this provider work?
I found this https://github.com/crossplane-contrib/provider-confluent/blob/main/cluster/test/setup.sh#L6 but its a bit of a guessing game what is contained in : "${UPTEST_CLOUD_CREDENTIALS}"
The text was updated successfully, but these errors were encountered: