-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: [S3] permissions when specifying custom kms (#1202)
* fix: [S3] permissions when specifying custom kms [#186276329](https://www.pivotaltracker.com/story/show/186276329) This commit implements the fix for the bug when enabling sse with a custom kms_key. We may want to investigate the consequences of the following scenarios not yet covered by any of the existing tests: - enabling/disabling sse after provisioning - creating multiple bindings - changing kms_key after provisioning * fix: [S3] allow safely updating default kms key [#186276329](https://www.pivotaltracker.com/story/show/186276329) This change allows customers to specify sse_extra_kms_key_ids as a comma-separated list of keys to be used for decryption. This is specially useful when rotating sse_default_kms_key_id since previous objects are not automatically reencrypted with the new key. When that happens, specifying any previous default_kms_key_id as part of sse_extra_kms_key_ids allows the binding to decryp any existing objects created with these extra keys, otherwise any read operation for such objects would fail. Extra keys will still be used for decryption if you decide to disable server-side-encryption but some of the objects in the bucket were created while encryption was enabled. * fix: [S3] corner-case when sse_all_kms_key_ids:"" [#186276329](https://www.pivotaltracker.com/story/show/186276329) Fix scenario when bind input includes sse_all_kms_key_ids: "" Currently, when that happens key_ids_list=[""] instead of [] therefore, count=length(key_ids_list) is 1 instead of 0 which is what we want. Compacting key_ids_list is an easy and mostly future proof fix. --------- Co-authored-by: Andrea Zucchini <zandrea@vmware.com>
- Loading branch information
1 parent
e74281f
commit 1b5699e
Showing
9 changed files
with
61 additions
and
6 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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