-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: Optional appName for tag #1497
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A really sensible change!
I wonder if we should rename the property to app
, and consequently rename app
in the constructor to scope
? scope
is a fairly typical name within the AWS CDK for this type of argument.
IIUC the patterns will add the app
tag to resources too, so I'd be curious to see what would happen if multiple GuEc2App
patterns are added to the same GuStack
and each set the app tag. Maybe that's worth a test and/or some validation logic?
The docstring for cdk/src/constructs/core/stack.ts Line 45 in 8b45ab3
But, as this PR suggests, for some reason this isn't actually done. cc @akash1810 @tomrf1 I wonder if we should just require |
I think the docs are out of date; we correct that description!
I don't think we can do this. Tags at the |
@akash1810 @nicl I've pushed up the rename from |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🏷️
🎉 This PR is included in version 48.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I don't think this is working, as we're never assigning |
It's useful to have all resources in a stack tagged with
App
, specifically for monitoring costs by app