Az.Cdn: Add post-migration endpoint cutover warnings - #30085
Open
Ptnan7 wants to merge 1 commit into
Open
Conversation
Contributor
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds post-migration endpoint cutover warnings to Az.Cdn migration commit cmdlets so users are reminded to update DNS/app references to the new Azure Front Door Standard/Premium endpoint and review the official migration guidance (including the April 1, 2028 cutover deadline).
Changes:
- Added a new
ChangeLog.mdentry describing the post-migration cutover guidance addition. - Emitted a success-oriented warning after the internal migration call for both cmdlets, with different wording for synchronous vs
-NoWait/-AsJob.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/Cdn/Cdn/ChangeLog.md | Documents the new post-migration cutover guidance warning behavior for upcoming release notes. |
| src/Cdn/Cdn.Autorest/custom/Invoke-AzCdnCommitProfileToAFDMigration.ps1 | Adds post-call warning messaging for CDN (classic) to AFD migration commit, with -NoWait/-AsJob wording. |
| src/Cdn/Cdn.Autorest/custom/Enable-AzFrontDoorCdnProfileMigration.ps1 | Adds post-call warning messaging for Front Door (classic) migration commit, with -NoWait/-AsJob wording. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+136
to
+140
| if ($NoWait -or $AsJob) { | ||
| Write-Warning("Migration request submitted successfully. After migration completes, traffic may still depend on the classic endpoint. Update your custom domain DNS or application references to use the new Azure Front Door Standard/Premium endpoint before April 1, 2028 to avoid any service disruption. Learn more: https://learn.microsoft.com/en-us/azure/cdn/migrate-tier?toc=/azure/frontdoor/toc.json.") | ||
| } else { | ||
| Write-Warning("Migration completed successfully. Traffic may still depend on the classic endpoint. Update your custom domain DNS or application references to use the new Azure Front Door Standard/Premium endpoint before April 1, 2028 to avoid any service disruption. Learn more: https://learn.microsoft.com/en-us/azure/cdn/migrate-tier?toc=/azure/frontdoor/toc.json.") | ||
| } |
Comment on lines
+141
to
+145
| if ($NoWait -or $AsJob) { | ||
| Write-Warning("Migration request submitted successfully. After migration completes, traffic may still depend on the classic endpoint. Update your custom domain DNS or application references to use the new Azure Front Door Standard/Premium endpoint before April 1, 2028 to avoid any service disruption. Learn more: https://learn.microsoft.com/en-us/azure/frontdoor/migrate-tier.") | ||
| } else { | ||
| Write-Warning("Migration completed successfully. Traffic may still depend on the classic endpoint. Update your custom domain DNS or application references to use the new Azure Front Door Standard/Premium endpoint before April 1, 2028 to avoid any service disruption. Learn more: https://learn.microsoft.com/en-us/azure/frontdoor/migrate-tier.") | ||
| } |
Member
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
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.
🤖 PR Validation —⚠️ Review suggested
️✔️Az.Accounts
Description
Adds post-migration endpoint cutover warnings to both Azure Front Door (classic) and Azure CDN from Microsoft (classic) migration commit cmdlets:
Enable-AzFrontDoorCdnProfileMigrationInvoke-AzCdnCommitProfileToAFDMigrationSynchronous calls report successful completion, while
-NoWaitand-AsJobreport successful request submission. The warnings direct customers to the corresponding product migration guidance and the April 1, 2028 endpoint cutover deadline.Related documentation:
Validation
git diff --checkpassed.build-module.ps1was attempted but could not reach compilation because NuGet restore failed to connect tohttps://api.nuget.org/v3/index.jsonwith a TLSHandshakeFailure.Mandatory Checklist
Please choose the target release of Azure PowerShell.
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriately