cassandra-medusa
cassandra-medusa copied to clipboard
thelastpickle
Add s3 canned ACL support
Changing default canned ACL[1] would be useful for situations where the S3 bucket is located in a different account. For S3, by default the object owner is the source AWS account where the object comes from [2]. This is a big limitation for a disaster recovery scenario where the restore could be done in a different account and requires to previously change the permissions to all objects in the bucket.
The default ACL value will remain as private.
[1] https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl [2] https://aws.amazon.com/premiumsupport/knowledge-center/s3-bucket-owner-access/
┆Issue is synchronized with this Jira Task by Unito ┆friendlyId: K8SSAND-1406 ┆priority: Medium
Hi @ivanmp91,
we had a small git problem which made us rewrite history in master...
Could you please reset your master branch and rebase this branch on top of it?
Thanks and sorry for the inconvenience!
Hi @ivanmp91,
we had a small git problem which made us rewrite history in
master... Could you please reset your master branch and rebase this branch on top of it?Thanks and sorry for the inconvenience!
Sure! This is done @adejanovski
Hi @ivanmp91,
there are a lot of commits in this PR that would need squashing and cleaning up.
Could you rebase on top of the latest master, drop the commits that are part of this PR but were not written by you, and squash the remaining commits into a single one?
I can do this for you if you're not at ease with this type of manipulations with git.
ouch there are some conflicts we need to handle before it can be merged.
