Closed tomkerkhove closed 5 years ago
Don't you think because you have a "dot" on your parameter name. Have you tried AppName instead
This is supported in ARM so this should work with Mesh as well
I think this is CLI bug and should work if you use the generic ARM deployment commands.
Specify the parameters using the following syntax. Please reopen the issue, if this does not work.
--parameters "{\"location\": {\"value\": \"eastus\"}}"
The parameter in the ARM template has a default value so it should not be passed and just take that one, please feel free to re-open as I think this is a CLI bug
@VipulM-MSFT I think you commented/closed on wrong issue. I think this is related to the parsing that is happening of the app to provide better status details after deployment completes.
@mattrowmsft Yeah, there does appear to be an issue with the way the CLI attempted to parse the error message but would not be the cause of the deployment failure. Given it still goes through ARM, you should be able to see the reason for the deployment failure using the "az group deployment show" cmd. The CLI issue here occurs after the deployment itself has already failed.
This is no longer the case as far as I know.
I'm currenly using an ARM template which has a parameter for the application name. Unfortunately this is causing the deployment to fail:
CLI Version
0.8.0rc2
Command
This is the command that was being used:
Error
ARM Template