Hey, I have a question: pulumi component resources and azure resource groups What’s the typical or recommended way to design the code? Should I create 1 RG per pulumi component resource, or is it better to have 1 resource group per stack?

I like to think of Azure resource groups as a group of resources required to run a single workload. That workload might be a networking stack for a production environment consisting of a vnet, subnet, vpn gateway etc. or an application workload consisting of a container app and some persistent storage services. Usually for me those are multiple ComponentResources.

Thank you, in my case this mostly equals to a stack. In AWS we have separate pulumi projects for the network and applicaitons. Which would roughly translate to azure as 1 rg per stack => all network in rg1, application in rg2. And the ComponentResources expect an input of the

resourceGroup

they live in.