[App Service] az webapp deploy, az webapp up: Enable enriched-errors for deployment failure logs by default#33669
Open
Shi1810 wants to merge 3 commits into
Open
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @Shi1810, |
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| webapp deploy | cmd webapp deploy update parameter enriched_errors: added property default=True |
||
| webapp up | cmd webapp up update parameter enriched_errors: added property default=True |
microsoft-github-policy-service
Bot
requested review from
jsntcy,
wangzelin007 and
yonzhan
microsoft-github-policy-service
Bot
added
Auto-Assign
Contributor
There was a problem hiding this comment.
Pull request overview
This PR aims to make context-enriched deployment failure diagnostics (--enriched-errors) enabled by default for App Service deployment experiences, specifically az webapp deploy and az webapp up, so users see richer failure logs unless they explicitly opt out.
Changes:
- Switches default
enriched_errorsbehavior in deployment entry points to be enabled by default. - Updates CLI parameter help text to state the new default and how to disable it.
- Updates OneDeploy parameter defaults to align with the new intended behavior.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
src/azure-cli/azure/cli/command_modules/appservice/custom.py |
Flips enriched_errors defaults in deployment helpers/params to aim for enriched errors on by default. |
src/azure-cli/azure/cli/command_modules/appservice/_params.py |
Updates --enriched-errors help text for webapp up and webapp deploy to communicate the new default/opt-out. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
vijaysaayi
approved these changes
Jun 29, 2026
Shi1810
requested review from
DanielMicrosoft,
Pan-Qi,
VeryEarly,
YangAn-microsoft and
necusjz
as code owners
prathambande
approved these changes
Jun 29, 2026
Collaborator
|
App Service |
Contributor
Author
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.
Related command
az webapp deployaz webapp upDescription
Currently, only raw error messages are logged in the event of deployment failures.
customers have access to the
--enriched-errorsfeature flag, allowing them to view detailed failure logs and resolve errors more efficiently.This feature flag is available for the az webapp deploy and az webapp up deployment commands.
With this PR, we are enabling
enriched-errorstrue by default, customer and disable it by givingenriched-errors false.Testing Guide
History Notes
[App Service]
az webapp up/deploy: Add--enriched-errors falseparameter to disable enriched deployment failure logThis 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.