-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[App Service] Fix #26920: az webapp deployment slot create: Make the created new slot has same VNet integration settings of source slot as Portal behavior
#30836
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
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @madsd, |
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
az webapp deployment slotcreate clone from prod - Fix #26920
az webapp deployment slotcreate clone from prod - Fix #26920az webapp deployment slot create clone from prod - Fix #26920
az webapp deployment slot create clone from prod - Fix #26920az webapp deployment slot create Fix #26920 (clone from prod)
|
Fixes: #26920 |
az webapp deployment slot create Fix #26920 (clone from prod)az webapp deployment slot create: make the command consistent with the portal behavior
az webapp deployment slot create: make the command consistent with the portal behavioraz webapp deployment slot create: Make the command consistent with the portal behavior
|
This PR causes CI failure: CI logs#30776 bumped The CI of this PR was run on 2025-02-18 and #30776 was merged on 2025-02-24. As it has been a long time since the CI was run, it should be triggered again before merging. See #28465 |
|
This PR has no description which doesn't comply with our guideline: https://github.com/Azure/azure-cli/tree/dev/doc/authoring_command_modules#format-pr-description |
az webapp deployment slot create: Make the command consistent with the portal behavioraz webapp deployment slot create: Make the created new slot has the same VNet integration settings as the source slot to keep consistent with Portal behavior
az webapp deployment slot create: Make the created new slot has the same VNet integration settings as the source slot to keep consistent with Portal behavioraz webapp deployment slot create: Make the created new slot has the same VNet integration settings as the source slot
az webapp deployment slot create: Make the created new slot has the same VNet integration settings as the source slotaz webapp deployment slot create: Make the created new slot has same VNet integration settings of source slot as Portal behavior
Related command
az webapp deployment slot createDescription
Fix issue: #26920
When using the
az webapp deployment slot createcommand to create a new slot, the new slot does not inherit the VNet integration settings from the source slot.However, when creating a new slot using the azure portal, the new slot has the same VNet integration settings as the source slot
So this PR is to make the created new slot has the same VNet integration settings as the source slot to keep consistent with Portal behavior
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.