-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
az dls cmd logs preview warning to stderr since new version which makes devops pipeline fail #9891
Comments
The DLS commands have always been in preview. It was not called out until the recent change. |
The How is this new feature disabled so that we can differentiate between an error and an informational notice? |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sumantmehtams |
Writing to std.err is a very common behavior across many CLI tools. The CI should not rely on the contents in std.err. The CI should check the exit code instead: https://github.com/Azure/azure-cli#exit-codes |
The problem is Powershell is not very friendly with programs writing to STDERR. I've spend half of my day trying to strip out what is written to STDERR and only keep the JSON output from STDOUT, but didn't find a solution yet. Any workaround at this point would be much appreciated. |
@igelineau Follow this thread for detailed conversations and some workarounds - microsoft/knack#166 |
Describe the bug
Command Name
az dls account list
Errors:
A dls-preview warning is shown when calling any az dls cmd, which is written to the std err output. The devops pipeline fails, as it is treated as an error.
Command group 'dls' is in preview. It may be changed/removed in a future release.
We came up with a temporary solution to write the error to the null device by adding
2> /dev/null
to each az dls cmd, so that the pipeline will succeed.To Reproduce:
Execute any az dls command. For example:
az dls account list --query {}
Expected Behavior
The dls commands were not in preview before, so we were suprised to find it in preview mode since the new version came out.
Environment Summary
Additional Context
The text was updated successfully, but these errors were encountered: