AllowResourceGroupCreation is ignored

[tommasodotNET]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I use Azure local provisioning to reference existing Azure resources. I've setup params as such

  "Azure": {
    "SubscriptionId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "AllowResourceGroupCreation": false,
    "Location": "eastus",
    "CredentialSource": "AzureCli"
  }

but still I find a randomly named resource group created in my subscription.

Expected Behavior

I expected no resource group to be created in my subscription.

Steps To Reproduce

tommasodotNET/agent-framework-aspire

Exceptions (if any)

No response

.NET Version info

.NET SDK:
Version: 10.0.100-rc.1.25451.107
Commit: 2db1f5ee2b
Workload version: 10.0.100-manifests.a6e8bec0
MSBuild version: 17.15.0-preview-25451-107+2db1f5ee2

Runtime Environment:
OS Name: Windows
OS Version: 10.0.26200
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\10.0.100-rc.1.25451.107\

Aspire version: 13.0.0-preview.1.25519.2

Anything else?

No response

[captainsafia]

This is a quirk of our provisioning context layer which doesn't currently have a way of knowing that all of the resources that you are referencing are existing resources. I see two ways we can fix this:

• Moving our implementation to support provisioning resource groups using Bicep instead of the ARM APIs. This will play nicely with our goal to model resource groups as Aspire resources in Support modeling Azure resource groups as Aspire resources #11037. That let's use evaluate whether or not we want to run that Bicep later on in the provisioning flow.
• Figure out if we can delay creating resource groups until the first resource needs to be provisioned and only provision it if that resource is not an existing resource.