You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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?
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
taskcat test run
The text was updated successfully, but these errors were encountered: