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

this is enforced by the upstream API I believe, we just consume it

<@UCWG26BH7> isn't this name only used by Pulumi though?
I'd understand if it was the `name` field inside the args object for the resource, but this is the "name" parameter that all Pulumi resources have, regardless of the cloud provider being used

I might have missed something of course - I'm still fairly new to Pulumi

So the name of inside the resource gets used as the `name` field with auto naming

so let's say you creating `new Project('project:dev')`

it creates a resource with name `project:dev-xxxxxx` which is still used for the API call

image.png

if you look at the API spec:
<https://cloud.google.com/resource-manager/reference/rest/v1/projects#resource:-project>

here's the allowed characters

Ahh thanks <@UCWG26BH7> - I didn't realise that auto-naming was a thing

there's some info here:
<https://www.pulumi.com/docs/troubleshooting/faq/#why-do-resource-names-have-random-hex-character-suffixes>

I'll have a read over that - thanks again!