feat: create cognito userpool client that exports both client ID and … #214
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…client secret to a kubernetes secret (connection details)
alxyok
requested review from
nabuskey,
vara-bonthu,
candonov,
csantanapr,
7navyasa,
johnphilips3 and
edgarsilva948
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…client secret to a kubernetes secret (connection details)
What does this PR do?
Introduces a new Crossplane Composition and an XRD for managing AWS Cognito User Pool Clients. The composition enables automated provisioning of UserPoolClient resources based on user-specified inputs and writes connection secrets for the client, including and especially both the client ID and client secret.
Motivation
The current version of the UserPoolClient in the cognito-idp family of providers by AWS only exports client ID as a connection detail. It does not support client secret, which makes it useless if you want to reuse both of those details in other kubernetes resources such as exporting those in two SSM parameters or a secret in Secrets Manager.
More
Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
Yes, I have added a new example under examples to support my PR
Yes, I have updated the docs for this feature
Yes, I have linked to an issue or feature request (applicable to PRs that solves a bug or a feature request)
Note:
For Moderators
Additional Notes