Update Azure.Provisioning to latest#6390
Conversation
NuGet.config
Outdated
| <add key="dotnet9" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json" /> | ||
| <add key="dotnet-libraries" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-libraries/nuget/v3/index.json" /> | ||
| <add key="dotnet9-transport" value="https://dnceng.pkgs.visualstudio.com/public/_packaging/dotnet9-transport/nuget/v3/index.json" /> | ||
| <add key="azure-sdk-devfeed" value="https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-net/nuget/v3/index.json" /> |
There was a problem hiding this comment.
These NuGet.config changes won't be merged. We won't merge this PR until the 1.0.0 versions are on nuget.org.
| { | ||
| var formatStringBuilder = new StringBuilder(); | ||
| var arguments = new List<BicepValue<string>>(); | ||
| var bicepStringBuilder = new BicepStringBuilder(); |
There was a problem hiding this comment.
FYI - @davidfowl. We aren't able to get rid of our Format string parsing code from ReferenceExpression. But we are able to use the new BicepStringBuilder here.
There was a problem hiding this comment.
I was able to simplify the BicepValueFormattableString class. No need for it to inherit from FormattableString.
There was a problem hiding this comment.
We should be able to if you move this logic into the caller right?
There was a problem hiding this comment.
I can build up the BicepStringBuilder earlier and not have the BicepValueFormattableString at all. But we will still need to parse the ReferenceExpression.Format string ourselves.
|
This should be fixed now. |
Respond to latest renames getting the API ready for GA release. Fix dotnet#6376
This hits an issue with `${null}` that is being fixed with Azure/azure-sdk-for-net#46742.
|
This is now ready for review. We have all the changes from the Azure.Provisioning libraries we need for 9.0.0 GA. |
|
/backport to release/9.0 |
|
Started backporting to release/9.0: https://github.com/dotnet/aspire/actions/runs/11511183771 |
|
/backport to release/9.0 |
|
Started backporting to release/9.0: https://github.com/dotnet/aspire/actions/runs/11521283799 |
…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 dotnet#6474
|
/backport to release/9.0 |
|
Started backporting to release/9.0: https://github.com/dotnet/aspire/actions/runs/11522041527 |
|
/backport to release/9.0 |
|
Started backporting to release/9.0: https://github.com/dotnet/aspire/actions/runs/11523011977 |
|
This has all the changes from [release/9.0] Update Azure.Provisioning to latest (dotnet/aspire#6489) merged into it. Looking for an approval so we can merge it into |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Description
Respond to latest renames getting the API ready for GA release.
Fix #6376
I'll use this PR until we get stable versions from @tg-msft.
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 because the APIs we need to fix the issue are being made public in this new Azure.Provisioning version.Fix #6474
Checklist
Microsoft Reviewers: Open in CodeFlow