This message was deleted.
# generals
sparse-intern-71089
04/15/2021, 11:52 AMThis message was deleted.
b
bored-oyster-3147
04/15/2021, 12:49 PMI've never done this but I would try declaring a
azureProviderawsProviderc
cool-fireman-90027
04/15/2021, 2:23 PMHere is an kubernetes-ts-multicloud example that has multiple different providers that you can view that will help out.
👀 1
h
hundreds-receptionist-31352
04/15/2021, 5:10 PMthanks I will take a look at that
l
little-cartoon-10569
04/15/2021, 6:01 PMI'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 PMYou 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 PMIf nothing else, this ensures that resources still work even if you forget to set their parent 🙂
b
bored-oyster-3147
04/15/2021, 6:38 PMresources inherit providers from their parent resourcesI actually didn't know this. My component resources have always just passed the provider all the way down 🤦♂️