No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I’m not aware of a way to do that without also giving up resource auto-naming. I typically use tags to help provide that sort of functionality, but I understand that’s not necessarily an ideal solution.

then, is there any suggestion regarding resource naming? maybe, the best is to name the resource as the variable?

That’s a pretty common approach. You could also use something like `fmt.Sprintf` (sorry, I tend to use Go most of the time) to build some sort of prefix or such into the resource name.

Resource autonaming supports the namePrefix property on many resources.

But tags is a good way to go. This is why AWS classic had defaultTags added to the provider.