-
Notifications
You must be signed in to change notification settings - Fork 86
feat: change KMS discovery keyring configuration path #228
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
Conversation
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.
I would add a test for your neither
case
|
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.
LGTM
raise TypeError("is_discovery cannot be True if key IDs are provided") | ||
|
||
if neither: | ||
raise TypeError("No key IDs provided") |
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.
You could mention discovery in the error message, something like "Key IDs are required for non-discovery KMS Keyrings.", so the user knows about discovery if they actually didn't want to supply key ids
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.
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.
ah, misread that; actually in the error message. Sure.
Issue #, if available:
resolves #227
Description of changes:
Reasoning is described in #227 and awslabs/aws-encryption-sdk-specification#84.
The short version is that rather than discovery being a derived property that is the result of an absence of key IDs, discovery is now an explicit parameter that is incompatible with key IDs being supplied.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable: