[ARM] BREAKING CHANGE: az bicep build/decompile: Change the --files parameter to --file

[shenglol]

Description

• Closes Bicep related live test issue #17390: Bicep related live test issue.
• Closes Validate scope when deploying a bicep file with Azure CLI / Azure Powershell bicep#1562: Validate scope when deploying a bicep file with Azure CLI.
• Partially addresses Bicep errors if I've hit my github api rate limit bicep#2055: Bicep errors if I've hit my github api rate limit.
• Changes the --files parameter to --file to only take one file for the az bicep build/decompile commands, because we removed the support of multi-file compiling/decompiling support from Bicep CLI. Closes Output directory support for az cli bicep module bicep#2010.

Testing Guide
az bicep build/decompile --file {bicep_file}

History Notes
[ARM] BREAKING CHANGE: az bicep build: Change the parameter --files to --file
[ARM] BREAKING CHANGE: az bicep decompile: Change the parameter --files to --file
[ARM] az bicep build: Add a parameter --outdir for specifying the output directory
[ARM] az bicep build: Add a parameter --outfile for specifying the output file path
[ARM] Fix an issue where checking version upgrade for Bicep CLI throws exception if GitHub API rate limit is hit

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

• I adhere to the Error Handling Guidelines.

[yonzhan]

ARM

[zhoxing-ms]

May I ask why the ttl of this cache is 10 minutes?

[shenglol]

Setting ttl to 10 minutes means it will sent at most 6 requests per hour, which is good enough to avoid GitHub throttling for anonymous requests (60 / hour / IP address). Other other hand, we do want the bicep commands to detect version upgrade of Bicep CLI as soon as we do a release, and I feel like 10 minute of delay is acceptable.

[shenglol]

This is still a workaround, though. CI/CD runs that depend on Bicep can still get throttled. We are also thinking about setting up CDN for caching the Bicep releases to completely eliminate the throttling issue.

[zhoxing-ms]

Got it, thanks~

[zhoxing-ms]

Changes the --files parameter to --file to only take one file for the az bicep build/decompile commands, because we removed the support of multi-file compiling/decompiling support from Bicep CLI.

I would like to ask why you do not support multiple files any more?

[shenglol]

le files any m

Changes the --files parameter to --file to only take one file for the az bicep build/decompile commands, because we removed the support of multi-file compiling/decompiling support from Bicep CLI.

I would like to ask why you do not support multiple files any more?

Because for bicep build, in some cases it could produce inconsistent/extra JSON templates if one of the files is a module referenced in another file. A build command should only take a main.bicep file and output one JSON template. Decompiling is less of a problem, but we want to keep the user experience consistent.