-
Notifications
You must be signed in to change notification settings - Fork 398
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 for aws_kms_info with external/custom key store keys #311
Conversation
Hi @PandaWill, Thanks for your contribution, the change looks solid and I've successfully run it through the integration tests to double check that the standard behaviour isn't broken. I agree that we can't easily add an integration test for this specific case, however please could you add a changelog entry: https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs-how-to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good
Please could you add a changelog entry: https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs-how-to
I've added the change-log fragment - I hope it's looks okay. Thanks for the speedy review. |
Thanks for your submission. For the future, an alternative would have been to catch the UnsupportedOperationException error. |
…lections#311) * Fix for aws_kms_info with external/custom key store keys * Added changelog fragment
…lections#311) * Fix for aws_kms_info with external/custom key store keys * Added changelog fragment
…lections#311) * Fix for aws_kms_info with external/custom key store keys * Added changelog fragment
…ons#311) add object ownership controls options for s3 bucket Reviewed-by: https://github.com/apps/ansible-zuul
SUMMARY
aws_kms_info raises an exception when used with a KMS key where the source of key material is external.
ISSUE TYPE
COMPONENT NAME
aws_kms_info
ADDITIONAL INFORMATION
The documentation states that these key types are not supported, https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html#rotate-keys-how-it-works
We don't have to handle the case for asymmetric keys because the KMS end-point just returns false. But we do have to handle the external/custom key store key cases:
Note I haven't added a regression test because aws_kms cannot create KMS keys with external key material.