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

Probably not a reason per se: the name of a resource is the key in a map. The value (resource object) doesn't really need the key.

The name is essentially part of the state, rather than part of the resource.

It would be really useful when creating resources based on other resources.

In a ComponentResource? I just pass the name straight through.

Yes of course that's what I want to do but then you end up having to push this extra parameter around and duplicate it all over the place

If you're constructing resources outside of the constructor, yes, you do currently have to do that :disappointed: Unless maybe you can duck-type the name somehow?

Yep, looks like this might be worth a try if you don't mind sneaking under the covers: `const internalName = (resource as any).__name;`

Usual caveat: may break without warning. Undocumented internal code. Etc.