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

fix(dynamodb): Resolve KMSMasterKeyArn for comparison #1907

Merged

Conversation

MisterMX
Copy link
Collaborator

Description of your changes

This adds an extra step in isUpToDate to resolve the ARN of the key that is referenced by whatever is given in spec.forProvider.sseSpecification.kmsMasterKeyId. This is necessary because AWS always returns the ARN even if the create or update call was made with an alias which triggered constant update calls.

Fixes #1440

This uses Gomock to mock the KMS client. I the same step I added a bunch of refactoring, like moving all mocks in the same package and splitting the API code generation from mock code generation.

I have:

  • Read and followed Crossplane's contribution process.
  • Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Unit tests and existing examples

@MisterMX MisterMX force-pushed the fix/dynamodb-kms-master-key-id branch from 0463018 to 03cf1e6 Compare October 13, 2023 14:43
Signed-off-by: Maximilian Blatt (external expert on behalf of DB Netz) <maximilian.blatt-extern@deutschebahn.com>
@MisterMX MisterMX force-pushed the fix/dynamodb-kms-master-key-id branch from 03cf1e6 to 7cbb96b Compare October 13, 2023 14:48
@MisterMX MisterMX merged commit ba8e8e0 into crossplane-contrib:master Oct 13, 2023
11 checks passed
@MisterMX MisterMX deleted the fix/dynamodb-kms-master-key-id branch October 13, 2023 15:32
@github-actions
Copy link

Successfully created backport PR #1911 for release-0.44.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot update dynamodb table with kms encryption
2 participants