-
Notifications
You must be signed in to change notification settings - Fork 342
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
add object ownership controls options for s3 bucket #311
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.
You've fallen foul of the sanity linter. We generally follow PEP8 as a formatting guide when it comes to spacing.
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
Co-authored-by: Mark Chappell <[email protected]>
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.
More whitespace cleanup
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.
even more...
We'll need a change to the storage permissions for our CI - https://github.com/mattclay/aws-terminator Specifically https://github.com/mattclay/aws-terminator/blob/master/aws/policy/storage-services.yaml |
S3 policy updated PR https://github.com/mattclay/aws-terminator/pull/142/files |
I've yet to take a look at the PR. |
recheck |
4 similar comments
recheck |
recheck |
recheck |
recheck |
tests/integration/targets/s3_bucket/roles/s3_bucket/tasks/ownership_controls.yml
Show resolved
Hide resolved
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 when the version_added is updated
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.
Just a minor nit. Once the extra deletion test is in place LGTM
tests/integration/targets/s3_bucket/roles/s3_bucket/tasks/ownership_controls.yml
Show resolved
Hide resolved
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.
Thanks for all your work on this @abikouo! tremble's last comment is addressed in this latest changeset so I'm going to gate this one.
For those using
It's due to this PR ;) |
…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
Depends-On: #345
SUMMARY
This feature would allow the bucket settting "Object Ownership" to be changed from the default of "Object writer" to "Bucket owner preferred". In conjunction with a bucket policy condition, this allows a bucket owner to ensure that all objects uploaded to a bucket are always owned by them.
#245
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION