Suggestion: Auto prefix names with some stack configuration value #1771
Labels
area/engine
Pulumi engine
impact/usability
Something that impacts users' ability to use the product easily and intuitively
kind/enhancement
Improvements or new features
Reported on the Community Slack:
This seems like a common pattern in practice, e.g. having several stacks with the same name but differentiated via suffix. e.g. "website-staging", "website-prod", etc.
One reason for resisting this type of thing in the past, was that anything that goes into the resource's name becomes part of its identity. And so if that "name prefix" were ever to change, then the resource would be considered different.
But between having a richer notion of resource identity (e.g. using a UUID instead of URN) and using a Stack's tags (e.g. the project field in Pulumi.yaml), we should be able to come up with something that makes sense in this area.
The text was updated successfully, but these errors were encountered: