You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running the az bicep decompile-params command and the specified --bicep-file already exists, the warning message suggests using --force parameter, which doesn't exist for that command.
To Reproduce
Steps to reproduce the behavior:
When running the az bicep decompile-params command and the specified --bicep-file already exists, I get a warning message saying:
The output path "path/to/file.bicepparam" already exists. Use --force to overwrite the existing file.
However, az bicep decompile-params doesn't have a --force parameter.
Additional context
I would expect that the error message is accurate, or even better - to add the force parameter to that command. Then it would have the same behaviour as the bicep build-params command.
The text was updated successfully, but these errors were encountered:
Bicep version
Bicep CLI version 0.27.1 (4b41cb6)
Describe the bug
When running the
az bicep decompile-params
command and the specified--bicep-file
already exists, the warning message suggests using --force parameter, which doesn't exist for that command.To Reproduce
Steps to reproduce the behavior:
When running the
az bicep decompile-params
command and the specified--bicep-file
already exists, I get a warning message saying:However,
az bicep decompile-params
doesn't have a--force
parameter.Additional context
I would expect that the error message is accurate, or even better - to add the force parameter to that command. Then it would have the same behaviour as the
bicep build-params
command.The text was updated successfully, but these errors were encountered: