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

Great question! I'll share my thoughts but would love to learn from others' experiences on this also.

I actually only learned recently that resource names _could_ be reused (as you note, across different types), so I tried it -- and honestly, while it made my CLI output look a lot tidier, it also confused me (when scanning CLI output, resource lists in the Cloud UI, the code itself, etc.) to have multiple different things using the same name. So in general, I've gone back to naming everything uniquely even across different resource types. Personal preference of course, but when my own code confuses me, I know I'm on the wrong path. :slightly_smiling_face:

Appreciate the input! Wondering about the same cleanliness/completeness tradeoff myself. I’m not sure how often (if ever) I’m referring to the name in isolation — nice to hear others experience in this same venture