Skip to content
New issue

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

LogGroup - allow updating kmsKeyID parameter #1991

Closed
wotolom opened this issue Jan 25, 2024 · 0 comments · Fixed by #1992
Closed

LogGroup - allow updating kmsKeyID parameter #1991

wotolom opened this issue Jan 25, 2024 · 0 comments · Fixed by #1992
Labels
enhancement New feature or request

Comments

@wotolom
Copy link
Contributor

wotolom commented Jan 25, 2024

What problem are you facing?

Currently a KMSKey can only be associated with a LogGroup on Creation.
Adding, removing, changing the kmsKeyID (== ARN) field does not trigger an update later on.

How could Crossplane help solve your problem?

Enhance controller to include checks for kmsKeyID changes, triggering update(), where kmsKeys are getting dissociated and/or associated

@wotolom wotolom added the enhancement New feature or request label Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant