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

yeah, resource name should be unique for a stack, otherwise there will be a conflict. I am not an expert, but I wouldn't recommend using `name` at all as pulumi provides great functionality to avoid a lot of issues such as `deleteaftercreate` errors and a lot more, which is called autonaming (second link) <https://www.pulumi.com/blog/infrastructure-as-code-resource-naming/>

<https://www.pulumi.com/docs/intro/concepts/programming-model/#autonaming>