Add s3:PutObjectTagging
permission to sponsored bucket
#183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This gives the production heroku user permission for the
PutObjectTagging
action, from the bucket policy itself. This actually solves the issue that #182 was attempting to solve. That change didn't work because permissions to the production bucket must be added on the bucket policy itself (because the bucket and user reside in two different accounts), and we were only adding that permission to the user itself, not the bucket.