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 was looking at this issue <https://github.com/pulumi/pulumi-yaml/issues/12> and is that the way that we are expected to specify versions of a provider to use for a resource? What about components with children, is that version propagated down? In the other languages we can kind of enforce this versioning via the relevant package managers.

Nevermind, I see that was a discussion which ended with the versioning being handled via provider resources

Not seeing how to do this with a provider created using the pulumi-go-provider

<@U040MMFMD37> If you are still stuck, could you elaborate a bit more on your use case?
Are you writing a Pulumi program in YAML? Are you writing a Pulumi provider in Go (using pulumi-go-provider)?

I am unstuck. <@U03MCHZARD0> helped me see that I needed to do pulumi:providers:{name}