Skip to content

Conversation

@zhoxing-ms
Copy link
Contributor

Issue: #12031

Because the SDK did not throw an exception when the status code of the service returned result is 400, the exit code is 0 when the verification fails.
I wrapped the error result returned by the verification as CLIError, so the exit code returned when the verification fails is 1.
The same error reason as #11842 occurs on several other commands.

History Notes:
(Fill in the following template if multiple notes are needed, otherwise PR title will be used for history note.)

[Component Name 1] (BREAKING CHANGE:) (az command:) make some customer-facing change.
[Component Name 2] (BREAKING CHANGE:) (az command:) make some customer-facing change.


This checklist is used to make sure that common guidelines for a pull request are followed.

@zhoxing-ms zhoxing-ms requested a review from Juliehzl as a code owner February 20, 2020 13:12
@zhoxing-ms zhoxing-ms requested a review from qianwens February 20, 2020 13:14
@yonzhan yonzhan added this to the S166 milestone Feb 20, 2020
@yonzhan
Copy link
Collaborator

yonzhan commented Feb 20, 2020

add to S166.

@zhoxing-ms zhoxing-ms force-pushed the deployment_validate_error_exitcode_0 branch from e4d7dce to 419be35 Compare February 26, 2020 01:27
@zhoxing-ms
Copy link
Contributor Author

This logic has been refactored and is now fixed in the new code.
PR: #10751

@zhoxing-ms zhoxing-ms closed this Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants