This message was deleted.

sparse-intern-71089

04/15/2021, 11:52 AM

This message was deleted.

bored-oyster-3147

04/15/2021, 12:49 PM

I've never done this but I would try declaring a

azureProvider

and an

awsProvider

and I would make sure to always pass them to the appropriate resource - is that what you're doing?

cool-fireman-90027

04/15/2021, 2:23 PM

Here is an kubernetes-ts-multicloud example that has multiple different providers that you can view that will help out.

👀 1

hundreds-receptionist-31352

04/15/2021, 5:10 PM

thanks I will take a look at that

little-cartoon-10569

04/15/2021, 6:01 PM

I've done it, it works a treat. You use exactly the same technique to deploy to different AWS regions.

little-cartoon-10569

04/15/2021, 6:03 PM

You need to be diligent about passing providers around. While resources inherit providers from their parent resources, I've found it's a good idea (from a code clarity point of view) to not rely on this, and instead pass the correct provider to every resource, always.

little-cartoon-10569

04/15/2021, 6:03 PM

If nothing else, this ensures that resources still work even if you forget to set their parent 🙂

bored-oyster-3147

04/15/2021, 6:38 PM

resources inherit providers from their parent resources

I actually didn't know this. My component resources have always just passed the provider all the way down 🤦‍♂️

Open in Slack

Previous Next

Pulumi Community

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.