Support modeling Azure resource groups as Aspire resources

[vhvb1989]

from issue: Azure/azure-dev#3550

Publishing Aspire to a Resource Group instead of to a Subscription is something that people would need to model in the AppHost. Similar to how people can model the Azure Container Environment, people should be able to target one specific RG to be created or to re-use.

[davidfowl]

More details? Deploying to an existing rg?

[vhvb1989]

Either to an existing RG or to a new RG which you can define in your apphost.

You could, for example, define one parameter and use it for selecting a rg. Azd would use that to list rg from your subscription and let users pick one to publish your app.

This is supported by azd, just need to be modeled in Aspire. Then azd would create a main.bicep scoped to rg deployment

[davidfowl]

@vhvb1989 Currently azd owns the resource group generation when using azd (main.bicep). Wouldn't this still be part of azd?

For aspire deploy/publish, this should be possible to change in the apphost.

[vhvb1989]

@davidfowl , yes, azd is providing a default resource group. However, what I am trying to avoid is introducing an azd-way to customize the resource group. Instead, whatever you make in the AppHost to customize your resource group should be understandable for Aspire deploy/publish as well as azd.

[davidfowl]

cc @captainsafia

[captainsafia]

We've talked about supporting this by modeling the resource group as a distinct resource in the application model that we can emit a Bicep template for.

When we do this, we'll need to rework aspects of our Bicep provisioning since the logic (like azd) currently assumes that the creation and customization of resource groups is owned by the deployment logic and not the Aspire app model.

[The3G]

@davidfowl @captainsafia is there any plans to support an AppHost that needs to use/deploy resources in different resource groups? I have a need for this due to a security policy (outside of my control) where the resources are split into different resource groups; according type and usage of the resource and the resources inside these are managed by different teams and are security graded accordingly.

[davidfowl]

You can already use resources from different resource groups but you can't deploy resources in different resource groups.

[The3G]

@davidfowl are there any plans to support the creation & deployment to mulitple Azure ResourceGroup(s), Subscription(s), Tenant(s) from an aspire project/solution? and/or what would be your view on this usecase for aspire and the azure provisioning/deployment story? has it value?

[davidfowl]

In the short term no, we're not optimizing for deploying to multiple resource groups. We're trying to solve the basics first. We'll support deploying to a single resource group and using resources from existing resouregroups, tenants and subscriptons.