Document Azure resource naming breaking change #1666
Labels
docs-experience
Indicates issues that are about the learn.microsoft.com experience or design [org][type][category]
in-pr
okr-freshness
OKR: Freshness of content
Pri1
High priority, do before Pri2 and Pri3
📌 seQUESTered
Identifies that an issue has been imported into Quest.
📦 release-9.0
Used to track doc updates for release 9.0 of .NET Aspire.
Milestone
In dotnet/aspire#5809, and as part of the move to the new Azure.Provisioning versions, we are making a change to how Azure resources are named.
See dotnet/aspire#5756 for the description of the problem / reasoning for the change.
To revert back to using the .NET Aspire v8 naming scheme, the following code can be added to the beginning of the AppHost's Program.cs:
@IEvangelist - We could also take this opportunity to document how to use the ProvisioningContext to customize the Azure resources created in an Aspire app. Do you want a separate issue tracking that? or is it OK to reuse this issue?
It would be great if we had a base set of documentation from the Azure SDK we could point to. cc @tg-msft
Associated WorkItem - 330865
The text was updated successfully, but these errors were encountered: