-
Notifications
You must be signed in to change notification settings - Fork 159
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
Does not seem to work with cross account s3 buckets #72
Comments
We are also seeing those problems. Once we have set a ACL to helm s3 push we get access denied when we try to publish new charts (upload chart to s3: upload object to s3: AccessDenied: Access Denied) |
Possibly related to #75 aws s3 cp s3://helm-chart-bucket/ s3://helm-chart-bucket/ --recursive --acl bucket-owner-full-control I was able to see a list of files that I did not have access to from the owner account. I purged those files and reindexed with We are in process of testing the solution, but I think this can be fixed by adding to the |
So note/hint for anyone else running on this, in order to achieve this properly on a private bucket, I had to...
aws s3 cp --recursive s3://s3-reponame-here/helm-charts/ s3://s3-reponame-here/helm-charts/ --grants full=id=redacted_account_canonical_id_here full=id=redacted_account_2_canonical_id_here full=id=redacted_account_3_canonical_id_here --metadata '{"x-last-updated-at":"`date +%s`"}' ^ Note you may not want all your accounts to have full access as I do above, use "read" instead where relevant |
Thanks @AndrewFarley this worked great. |
I tried setting up the plugin to use cross account s3 buckets and it doesn't seem to work. Using the aws cli works just fine for fetching charts, but the plugin returns an access denied error.
The text was updated successfully, but these errors were encountered: