Azure CLI az bicep decompile-params command gives inaccurate error message

[martin-kirilov]

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:

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.

[polatengin]

Quick update: the --force flag already exists in the Bicep CLI, but the Azure CLI command doesn't map/pass it through today. I've opened a PR to add that mapping so az bicep decompile-params --force will work and forward the flag to the Bicep CLI: Azure/azure-cli#32739

Once this merges, the warning message will be accurate, and users will be able to overwrite with --force.

I'll keep an eye on the PR and update here when it lands.

[brendandburns]

Looks like Azure/azure-cli#32739 merged so I think this probably can be closed.