[Regression] `--stdout` does not work for `az bicep build` in v2.37.0

[ellismg]

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
az bicep build

Describe the bug
Since v2.37.0 the --no-restore flag has to be passed to bicep build, as well as --stdout to for the compiled template to be printed.

To Reproduce
run az bicep build --stdout -f <path-to-bicep> and you'll see not output. Add --no-restore and you will.

Additional context
It was introduced, I think, with 215960c.

Note that previously, when --stdout was set, we would print the result of calling run_bicep_command. When the restore feature was added, the extra if block that was introduced meant that we only printed the result when --no-restore was also set.

Thank you for your feedback. This has been routed to the support team for assistance.

[yonzhan]

route to CXP team

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @josephkwchan, @jennyhunter-msft.

Issue Details

---

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
az bicep build

Describe the bug
Since v2.37.0 the --no-restore flag has to be passed to bicep build, as well as --stdout to for the compiled template to be printed.

To Reproduce
run az bicep build --stdout -f <path-to-bicep> and you'll see not output. Add --no-restore and you will.

Additional context
It was introduced, I think, with 215960c.

Note that previously, when --stdout was set, we would print the result of calling run_bicep_command. When the restore feature was added, the extra if block that was introduced meant that we only printed the result when --no-restore was also set.

Author:	ellismg
Assignees:	-
Labels:	Service Attention, ARM
Milestone:	-

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @satyavel, @apclouds.

Issue Details

---

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
az bicep build

Describe the bug
Since v2.37.0 the --no-restore flag has to be passed to bicep build, as well as --stdout to for the compiled template to be printed.

To Reproduce
run az bicep build --stdout -f <path-to-bicep> and you'll see not output. Add --no-restore and you will.

Additional context
It was introduced, I think, with 215960c.

Note that previously, when --stdout was set, we would print the result of calling run_bicep_command. When the restore feature was added, the extra if block that was introduced meant that we only printed the result when --no-restore was also set.

Author:	ellismg
Assignees:	-
Labels:	Service Attention, ARM - Templates
Milestone:	-

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @josephkwchan, @jennyhunter-msft.

Issue Details

---

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
az bicep build

Describe the bug
Since v2.37.0 the --no-restore flag has to be passed to bicep build, as well as --stdout to for the compiled template to be printed.

To Reproduce
run az bicep build --stdout -f <path-to-bicep> and you'll see not output. Add --no-restore and you will.

Additional context
It was introduced, I think, with 215960c.

Note that previously, when --stdout was set, we would print the result of calling run_bicep_command. When the restore feature was added, the extra if block that was introduced meant that we only printed the result when --no-restore was also set.

Author:	ellismg
Assignees:	-
Labels:	Service Attention, ARM, ARM - Templates
Milestone:	-