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 do not think it's supposed to work this way. provider parameter requires an instance of a `ProviderResource`
This means that you need to instantiate the provider in the same stack.

I do not think it would be a good pattern to instantiate providers somewhere else.

this means that in a micro-stack setup you need providers decribed within every stack which can sometimes be an issue when multiple people with different versions of pulumi installed wind up toggling the provider version back and forth… i was trying to escape from this situation by defining a single set of providers which is only updated once each new pulumi_aws version is released

This should not be an issue, because the stack is supposed to be an independent unit of resources.
Stack References provide only input values.

And you can pin the version of providers in `requirements.txt`