Update Azure provisioning CDN and Kusto to beta.3 - #20188
Draft
Jose Perez Rodriguez (joperezr) wants to merge 1 commit into
Draft
Jose Perez Rodriguez (joperezr) wants to merge 1 commit into
Jose Perez Rodriguez (joperezr) wants to merge 1 commit into
Conversation
Preserve Front Door and Kusto resource names while updating Azure.Provisioning.Cdn and Azure.Provisioning.Kusto to beta.3, and refresh the affected provisioning snapshots for the new Kusto API version. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 20188Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 20188" |
github-actions
Bot
added
the
area-integrations
Jose Perez Rodriguez (joperezr)
added
the
breaking-change
Copilot started reviewing on behalf of
Jose Perez Rodriguez (joperezr)
September 16, 2026 20:58
View session
Contributor
Tests selectorSelects the full PR test matrix + all PR-gated jobs (ALL) — a rule matching 'Directory.Packages.props' selects ALL Selection computed for commit |
14 tasks
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
Naming compatibility and the intentional Kusto API-version change have focused snapshot coverage; only a non-blocking tracking-comment improvement remains.
Review effort: Balanced (auto)
Findings: 1
Note
Copilot is running an experiment and ran this review at Balanced.
Open (1)
What changed in this PR
Updates CDN and Kusto provisioning dependencies while preserving existing Azure resource names.
Changes:
- Upgrades required Azure provisioning packages.
- Preserves legacy Front Door and Kusto naming.
- Updates Bicep snapshots for Kusto API
2025-02-14.
| File | Description |
|---|---|
Directory.Packages.props |
Updates provisioning dependency versions. |
src/Aspire.Hosting.Azure.FrontDoor/AzureFrontDoorExtensions.cs |
Preserves Front Door resource names. |
src/Aspire.Hosting.Azure.Kusto/AzureKustoBuilderExtensions.cs |
Preserves Kusto cluster names. |
tests/Aspire.Hosting.Azure.Tests/Snapshots/AzureFrontDoorTests.AddAzureFrontDoorWithSingleOriginGeneratesBicep.verified.bicep |
Updates single-origin output. |
tests/Aspire.Hosting.Azure.Tests/Snapshots/AzureFrontDoorTests.AddAzureFrontDoorWithMultipleOriginsGeneratesBicep.verified.bicep |
Updates multi-origin output. |
tests/Aspire.Hosting.Azure.Tests/Snapshots/AzureKustoExtensionsTests.AddAzureKustoCluster#00.verified.bicep |
Updates new-cluster output. |
tests/Aspire.Hosting.Azure.Tests/Snapshots/AzureKustoExtensionsTests.AddAzureKustoCluster#01.verified.bicep |
Updates role-assignment output. |
tests/Aspire.Hosting.Azure.Tests/Snapshots/AzureKustoExtensionsTests.AddAsExistingResource_RespectsExistingAzureResourceAnnotation_ForAzureKustoClusterResource.verified.bicep |
Updates existing-cluster output. |
tests/Aspire.Hosting.Azure.Tests/Snapshots/RoleAssignmentTests.KustoSupport.verified.bicep |
Updates Kusto RBAC output. |
Comment on lines
+23
to
+25
| // Azure.Provisioning.Cdn beta.3 regressed the beta.2 name templates and length limits for Front Door resources. | ||
| // Preserve the beta.2 Azure names here so dependency upgrades do not rename deployed profiles, endpoints, | ||
| // origin groups, origins, or routes and trigger avoidable infrastructure replacement. |
Contributor
|
Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Split the Azure provisioning upgrades that were held back from #20046 into an independently reviewable rollback path. This updates only
Azure.Provisioning.CdnandAzure.Provisioning.Kustoto1.0.0-beta.3, plus the required central dependency floors and affected provisioning snapshots.The customer-breaking part of the CDN update is the beta.3 TypeSpec generator regression: it drops the beta.2 resource-name templates and falls back to shorter 24-character limits for Front Door profiles, endpoints, origin groups, origins, and routes. This PR explicitly preserves the beta.2 Azure names in
Aspire.Hosting.Azure.FrontDoorso existing deployments do not rename or replace those resources when consumers take the package update.The Kusto update still changes generated provisioning output because
Azure.Provisioning.Kustobeta.3 removes older resource API versions and now emitsMicrosoft.Kusto/*@2025-02-14. This PR preserves the previous cluster naming pattern (kusto${uniqueString(...)}instead of the newkusto-${...}) so upgrades stay in-place where the newer API version is supported, while surfacing the remaining deployment compatibility break explicitly for review.Breaking changes
Aspire.Hosting.Azure.Kustopublish output now emitsMicrosoft.Kusto/clusters,databases, andprincipalAssignmentsat API version2025-02-14. Users deploying generated artifacts into environments, policies, or clouds that only allow2024-04-13must remain on the beta.2 package line until upstream compatibility is available, or roll back this PR's package changes. Front Door resource renames were intentionally prevented in this PR, so the remaining break is the Kusto API-version floor rather than resource replacement.Validation
dotnet test .\tests\Aspire.Hosting.Azure.Tests\Aspire.Hosting.Azure.Tests.csproj --no-launch-profile -- --filter-method "*.AddAzureFrontDoorWithSingleOriginGeneratesBicep" --filter-method "*.AddAzureFrontDoorWithMultipleOriginsGeneratesBicep" --filter-method "*.AddAzureKustoCluster" --filter-method "*.AddAsExistingResource_RespectsExistingAzureResourceAnnotation_ForAzureKustoClusterResource" --filter-method "*.KustoSupport" --filter-not-trait "quarantined=true" --filter-not-trait "outerloop=true"dotnet test .\tests\Aspire.Hosting.Azure.Kusto.Tests\Aspire.Hosting.Azure.Kusto.Tests.csproj --no-launch-profile -- --filter-not-class "*.KustoFunctionalTests" --filter-not-trait "quarantined=true" --filter-not-trait "outerloop=true"dotnet test .\tests\Aspire.Hosting.Azure.Kusto.Tests\Aspire.Hosting.Azure.Kusto.Tests.csproj --no-launch-profile -- --filter-not-trait "quarantined=true" --filter-not-trait "outerloop=true"fails in this environment because Docker is unhealthy (failed to connect to the docker API at npipe:////./pipe/dockerDesktopLinuxEngine), so I did not claim emulator validation.Fixes # (issue)
Checklist
<remarks />and<code />elements on your triple slash comments?