Skip to content
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.

Read resource_configuration from non-VM Deployments #68

Open
marratj opened this issue May 6, 2020 · 0 comments
Open

Read resource_configuration from non-VM Deployments #68

marratj opened this issue May 6, 2020 · 0 comments

Comments

@marratj
Copy link

marratj commented May 6, 2020

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant