Open yaegashi opened 6 months ago
The suspicious part in BicepUtility.cs:
Thanks for the feedback. Let me loop in deployment team.
One possibility is that output.Stderr
contained whitespace characters.
I'm seeing the same thing. Thank goodness I came across this issue because I thought I was going crazy!
Kindly ping @Azure/deployments-owners This could probably be fixed by replacing IsNullOrEmpty with IsNullOrWhiteSpace (needs validation). Also worth checking why bicep outputs white space characters in error stream.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/deployments-owners.
Description
The AzDeployment cmdlets (including New-AzSubscriptionDeployment, Test-AzSubscriptionDeployment, etc.) consistently emit an unexpected empty WARNING line to the console when using any Bicep input files that do not contain any errors or warnings.
The Bicep process does not output any errors or warnings to stderr.
No WARNING lines should be expected when valid Bicep inputs without any errors or warnings are used.
Issue script & Debug output
Environment data
Module versions
Error output
No response