-
Notifications
You must be signed in to change notification settings - Fork 3.2k
az bicep decompile: add exit code for warning errors #25009
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
Comments
Thank you for your feedback. This has been routed to the support team for assistance. |
route to CXP team |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @josephkwchan, @jennyhunter-msft. Issue DetailsRelated command Is your feature request related to a problem? Please describe. I'm using this command to validate my ARM templates as part of azure pipelines. Describe the solution you'd like Describe alternatives you've considered Additional context
|
Adding Service team, to look into this. @josephkwchan, @jennyhunter-msft Could you please look into this once you get a chance ? |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @satyavel, @apclouds. Issue DetailsRelated command Is your feature request related to a problem? Please describe. I'm using this command to validate my ARM templates as part of azure pipelines. Describe the solution you'd like Describe alternatives you've considered Additional context
|
Related command
az bicep decompile
Is your feature request related to a problem? Please describe.
Similar to PowerShell/PSScriptAnalyzer#840
az bicep decompile
seems to always return exit code 0 or at least for warningsthere should be an option to detect warning so it can update status appropriately in azure-pipelines
https://learn.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands?view=azure-devops&tabs=bash
I'm using this command to validate my ARM templates as part of azure pipelines.
Describe the solution you'd like
Either by default, either with an option, it should be possible an exit code that could match a pipeline status (success, warn, fail/error...)
Describe alternatives you've considered
An alternative would be trapping command output and search for warning.
Additional context
N/A
The text was updated successfully, but these errors were encountered: