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

there currently isn't, short of using different stacks and passing providers that way

different stack means different pulumi programs and thus different runs right ?

Alternatively with some code organization you could limit the number of times you need to explicitly pass your provider because <https://www.pulumi.com/docs/intro/concepts/resources/#inheriting-resource-providers|ComponentResources enabling inheriting resource providers>. But this just means that in your component resource you will be doing `ResourceOptions(parent=this)` for all resources instead

I kinda like this because the parent relationship I already have in place :slightly_smiling_face:

It actually sounds like the ComponentResource is a good container to hold various other common settings