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
{{ message }}
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
When we create deployment from a blueprint that contains vCenter VMs (resourceType == sdk.InfrastructureVirtual) then the provider reads the content[].data{} back from the deployment and puts it into resource_configuration blocks in the state file.
We still like to read back resource_configuration details also for XaaS software components, but for any non-VM deployments, this is not yet implemented.
There also seems to be a difference in how the vRA API responds when reading a Deployment. When VMs are part of the blueprint, they seem to be direct children of the deployment. They are directly listed within content[] of the resourceViews response together with the deployment itself. However, when there are XaaS components in the blueprint, they are not listed within content[] of the resourceViews response, only the deployment itself.
The non-VM components still can be retrieved via the GET: Child Resources link from the response, so the TF provider would be needed to be expanded with this.
The text was updated successfully, but these errors were encountered:
When we create deployment from a blueprint that contains vCenter VMs (
resourceType == sdk.InfrastructureVirtual
) then the provider reads thecontent[].data{}
back from the deployment and puts it intoresource_configuration
blocks in the state file.We still like to read back
resource_configuration
details also for XaaS software components, but for any non-VM deployments, this is not yet implemented.There also seems to be a difference in how the vRA API responds when reading a Deployment. When VMs are part of the blueprint, they seem to be direct children of the deployment. They are directly listed within
content[]
of theresourceViews
response together with the deployment itself. However, when there are XaaS components in the blueprint, they are not listed withincontent[]
of theresourceViews
response, only the deployment itself.The non-VM components still can be retrieved via the
GET: Child Resources
link from the response, so the TF provider would be needed to be expanded with this.The text was updated successfully, but these errors were encountered: