Describe the bug
With the latest CLI version (2.37.0) used by the ubuntu-20.04 agents, a bug was introduced that renders the output of the 'az bicep build --f (..) --stdout' command empty, unless an additional '--no-restore' flag is passed along with it.
This is very bad, as the function is used by all our Pester tests (alongside some other logic).
This bug was already brought up here
And a Pull Request to fix it is open here
For the time being, we can either try to downgrade the CLI version in our pipeline (to e.g. 2.28.0), use the '--no-restore' flag (which may have side-effects) or wait until the PR is merged and the agents updated.
To reproduce
Run any template with the 'az bicep build --f (..) --stdout' command. The result will be empty.
Code snippet
az bicep build --f (..) --stdout
Relevant log output
No response
Describe the bug
With the latest CLI version (2.37.0) used by the ubuntu-20.04 agents, a bug was introduced that renders the output of the
'az bicep build --f (..) --stdout'command empty, unless an additional'--no-restore'flag is passed along with it.This is very bad, as the function is used by all our Pester tests (alongside some other logic).
This bug was already brought up here
--stdoutdoes not work foraz bicep buildin v2.37.0 azure-cli#22621And a Pull Request to fix it is open here
az bicep build: Fix #22621:--stdoutdoes not work azure-cli#22685For the time being, we can either try to downgrade the CLI version in our pipeline (to e.g. 2.28.0), use the
'--no-restore'flag (which may have side-effects) or wait until the PR is merged and the agents updated.To reproduce
Run any template with the
'az bicep build --f (..) --stdout'command. The result will be empty.Code snippet
Relevant log output
No response