Skip to content
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

[Feature Request] Add possibility to set custom tags for staging S3 buckets #713

Open
Enigo opened this issue Jan 11, 2022 · 2 comments
Open

Comments

@Enigo
Copy link

Enigo commented Jan 11, 2022

Whenever taskcat test runs it creates staging S3 buckets with the CF templates under test.
To what I can see the bucket name pattern is "tcat-project_name-rndmchars".
Those buckets are created with tag taskcat-id (see screenshot).

But for reporting/tracking reasons it would be beneficial if

  • either the tags from corresponding CF are propagated to S3 bucket or
  • there is a command line argument for taskcat test run

123

@andrew-glenn
Copy link
Collaborator

This is a bit more complicated than meets the eye, namely due to the multiple permutations of bucket naming formats we have.

The format you're using is "legacy", (ex: s3_regional_buckets is False (default)), so a new bucket is created every time.

When the bucket is created, applying the CF tags to the bucket is pretty straight forward. However things become less ideal with Regional Buckets (s3_regional_buckets: true) or BYO bucket.

With that in mind, this feature would only apply to newly created buckets if regional buckets is turned off.

Any concerns? If not, I'll add this to the list and prioritize for the next sprint

@Enigo
Copy link
Author

Enigo commented Jan 11, 2022

so, basically you are saying that the feature will apply to the "legacy" case only (which is also my case)?
as such I have no concerns but just curious - it is called "legacy" for a reason, I assume. Is it scheduled for deletion?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants