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've never managed to sort this. In one case, we've resorted to passing a provider as an arg instead of an opt, specifically because of this!

Often, a reworking of classes can resolve this, so that all the resources that need to use one flavour of a provider get put into a single component resource, and all the ones that use a different flavour are in a different component. But that's not always possible.

For example, AWS Backup and remote backups do work nicely with this, we have a LocalBackup component and a RemoteBackup component. The ARN from the vault in the RemoteBackup is passed as a constructor arg to the LocalBackup, which creates the plans locally to backup and copy to the remote. Problem solved.

yeah i've gone the way of passing providers via args

i guess these are parts of pulumi's growing pains