Optionally specify resource suffix

[ferguscan]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

During local development, I use Pulumi to deploy resources to localstack. I want these resources to have predictable names, so I can easily interact with them via test scripts, etc.

On the other hand, when I deploy my infrastructure to AWS, I want my resources to have unique names (Pulumi's default behaviour). For this reason, I don't want to manually specify a name for each of my resources.

Instead, I would like to be able to (optionally) control the suffix that Pulumi applies to resource names. For my local deployment, i would specify a known, predictable suffix (e.g. dev). When deploying to AWS, I would not specify a suffix at all (letting Pulumi choose a random suffix, as per usual).

Affected area/feature

Unknown

[Frassle]

Duplicate of #1518. Long standing issue but due to the distributed and non-systemic way names are handled today it's a tricky one to fix.

[wouter-b]

Well four years later, the first issue I encountered when starting with pulumi today ;-)