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
My current version of Terraform is 1.5.3, and I'm using the vRA provider version 0.7.3. I've encountered an issue when attempting to deploy the vra_deployment resource using a blueprint ID. I'm encountering the following error:
Error: json: cannot unmarshal number 30.0 into the Go struct field PropertyDefinition.properties.minimum of type int64.
Interestingly, I can successfully deploy the same resource using the catalog ID. Could someone please confirm whether this issue is known in vRA 8.13?
The text was updated successfully, but these errors were encountered:
Unfortunately all of our deployments were made (hundreds) using deployment_id. If we switch over to catalog_item with an existing item it triggers a destroy and rebuild.
A little birdie has told me that VMware is aware of this problem and it will be patched with 8.14.1 of VRA. Not ETA on that release but roughly late November, maybe?
tenthirtyam
changed the title
A potential bug: I can't deploy a vra_deployment ressource on VRA 8.13
error deploying r/vra_deployment` on 8.13
Jul 10, 2024
tenthirtyam
changed the title
error deploying r/vra_deployment` on 8.13
error deploying r/vra_deployment on 8.13
Jul 10, 2024
tenthirtyam
changed the title
error deploying r/vra_deployment on 8.13
error deploying r/vra_deploymentJul 10, 2024
Hello folks,
My current version of Terraform is 1.5.3, and I'm using the vRA provider version 0.7.3. I've encountered an issue when attempting to deploy the vra_deployment resource using a blueprint ID. I'm encountering the following error:
Error: json: cannot unmarshal number 30.0 into the Go struct field PropertyDefinition.properties.minimum of type int64.
Interestingly, I can successfully deploy the same resource using the catalog ID. Could someone please confirm whether this issue is known in vRA 8.13?
The text was updated successfully, but these errors were encountered: