AWS S3 object tagging about issue-tracker HOT 5 CLOSED

Yes, you can configure one single storage for all 250 repos, and configure the HTTP header using the placeholder like in the example below:

x-amz-tagging: repository={{ repositoryName }}

the "{{ repositoryName }}" placeholder will be replaced with the name of repository that is being processed.

But please wait until we implement that placeholder and release it to production.

from issue-tracker.

Dear @m477r1x,
There is an in-buit customization of HTTP headers for that purpose. You can add a new x-amz-tagging HTTP header into your storage configuration, for example:

x-amz-tagging: repository=<thing>

The only issue is to get the name of repository that is being processed. We currently doesn't support that. The proposal it to implement it using templating, like in the example below:

x-amz-tagging: repository={{ repositoryName }}

Screenshot for reference:

from issue-tracker.

Amazing! I didn't know about this feature, sorry to have logged a feature request for something which is already implemented 🙂

Any chance I can parametarise it as a bulk action? Instead of setting the tag individually accross 250 repos 😅

from issue-tracker.

Dear @m477r1x,

We released it to the production environment. Please try the following format and let us know if it works for you:

x-amz-tagging: repository={{ context.RepositoryName }}

Reference:

• https://docs.cloudback.it/features/s3-object-tag/

from issue-tracker.

@m477r1x please note, that you need to grant s3:PutObjectTagging permission at a bucket level and at an access point level if you use access points.

from issue-tracker.