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
Error: failed to wait for creation of Managed Application "CBD" (Resource Group "CBS-Resourcegroup"): Code="ApplianceProvisioningFailed" Message="Deployment template validation failed: 'Template parameter JToken type is not valid. Expected 'Boolean'. Actual 'String'. Please see https://aka.ms/resource-manager-parameter-files for usage details.'." AdditionalInfo=[{"info":{"lineNumber":48,"linePosition":20,"path":"parameters.setupHA"},"type":"TemplateViolation"}]
Expected Behavior
Be able to specify parameters properly with type. Today all the params are getting converted to a string. While it works for what we have in the documented examples, there are managed applications waiting for non-string vals.
Actual Behavior
All the values are getting converted to a string causing deployment issues for apps waiting for other kind of parameter types.
Steps to Reproduce
We tried to deploy Pure CBS closed beta as a Managed App. I strongly believe there can be other managed apps waiting for non-string parameters.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Affected Resource(s)
azurerm_managed_application
Terraform Configuration Files
Error message
Error: failed to wait for creation of Managed Application "CBD" (Resource Group "CBS-Resourcegroup"): Code="ApplianceProvisioningFailed" Message="Deployment template validation failed: 'Template parameter JToken type is not valid. Expected 'Boolean'. Actual 'String'. Please see https://aka.ms/resource-manager-parameter-files for usage details.'." AdditionalInfo=[{"info":{"lineNumber":48,"linePosition":20,"path":"parameters.setupHA"},"type":"TemplateViolation"}]
Expected Behavior
Be able to specify parameters properly with type. Today all the params are getting converted to a string. While it works for what we have in the documented examples, there are managed applications waiting for non-string vals.
Actual Behavior
All the values are getting converted to a string causing deployment issues for apps waiting for other kind of parameter types.
Steps to Reproduce
We tried to deploy Pure CBS closed beta as a Managed App. I strongly believe there can be other managed apps waiting for non-string parameters.
The text was updated successfully, but these errors were encountered: