-
Notifications
You must be signed in to change notification settings - Fork 756
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
Bicep 0.4.412 always writes to standard error #3638
Comments
I've tried to mitigate this by downgrading to an older bicep version, however that now fails is it writes a helpful out of date warning to std error 😂
|
Having the same issue with Azure/arm-deploy and with the Azure CLI (Azure/arm-deploy#70 (comment)) |
Same issue, my temporary workaround is to remove failOnStderr:true, not ideal! |
This is caused by the new build summary capability that was added in #3195. The AZ CLI and AZ PS have to be modified to pass the |
Can you try installing an older version in the meantime?
|
@alex-frankel since the older version now writes an upgrade message to stderr so that is also broken
|
The version warning is coming from Az CLI and not from Bicep CLI, so we will need to deal with it separately. We will modify Bicep CLI to stop emitting the summary and cut a new release this week. |
New release with the fix should come by the end of this week (most likely sooner). |
My builds are working again with this morning's 0.4.451 release. Thanks @majastrz for the quick turn around. |
np - glad it's working now. |
Bicep version
Bicep CLI version 0.4.412 (f1169d0)
Describe the bug
In our pipeline, we build our bicep template before deploying it. We want to get behaviour similar to .Net's "Warning as Errors", so we've configured our task to fail if anything is written to standard error. This worked in previous bicep versions, however the latest bicep version has broken this as it appears to write the following text to standard error
To Reproduce
Have a devops task like the following, and attempt to build a valid bicep file. That task will error, even if bicep hasn't failed.
Additional context
In #3285, I can see the recommendation is to look for Exit Code rather than look at standard error, but that a build with warnings still produces an exit code of
0
.Do you have an alternative recommendation for how to fail on warnings
The text was updated successfully, but these errors were encountered: