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.
This gives the production heroku user permission for the
PutObjectTaggingaction, 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.