-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/9.0] Update Azure.Provisioning to latest #6489
Conversation
/azp run dotnet.aspire |
Azure Pipelines successfully started running 1 pipeline(s). |
b8fa9af
to
eaffd06
Compare
Respond to latest renames getting the API ready for GA release. Fix #6376
This hits an issue with `${null}` that is being fixed with Azure/azure-sdk-for-net#46742.
…has a dash. In .NET Aspire 8.x, when the Aspire resource name has dashes, we used those dashes in the Azure resource name. But we are incorrectly converting them to underscores. Fix #6474
eaffd06
to
2e9d07b
Compare
We knew this is coming and it is needed for the release. Approved. |
@eerhardt let me know when this is ready to merge. |
/azp run dotnet.aspire |
Azure Pipelines successfully started running 1 pipeline(s). |
@eerhardt were you planning to make more changes here or is this ready to go? |
We just got the stable packages pushed to nuget.org. I'm updating this with the stable dependencies and removing the nuget.config entries. Then it will be ready to merge. UPDATE: I see you did part of this above. I just need to remove the test nuget.config changes. |
Let’s gooo |
Backport of #6390 to release/9.0
/cc @eerhardt
Customer Impact
We need to use the GA version of the Azure.Provisioning libraries, so we can ship our
Aspire.Hosting.Azure*
packages as stable.Also fix an issue when using dashes
-
in resource names and usingAspireV8ResourceNamePropertyResolver
. We are prematurely converting the dash to an underscore, and the Azure resource name is not the same as it was in v8. This needs to be fixed together with this change because the APIs we need to fix the issue are being made public in this new Azure.Provisioning version.Fix #6474
Testing
Automated unit tests in repo still pass with the same bicep output.
Risk
There is some low risk in the new version of Azure.Provisioning, but all our tests are passing.
Regression?
No
Microsoft Reviewers: Open in CodeFlow