I have a question on how Terraform should/could handle this situation with a provider. I have a case where a VM is created via one resource and a vNIC can be added to that VM via another resource. My question is related to the vNIC second resource. That resource has a rather limited configuration argument set. Behind that vNIC resource the provider is calling this API on the backend hypervisor:
/api/antlets/antlet-name/vnics
However, the vNIC resource does not have a antlet-name configuration argument. I bolded the antlet-name as something the Provider is calling but I can’t seem to find a way to influence that value.
So my question is can Terraform call the vNIC resource and instrument the vNIC API URL appropriately via the Terraform file setup ? The resource itself looks like this:
resource antsle_vnics {
source = “br0”
type = “bridge”
}
But as mentioned above, this vNIC resource swagger definition doesn’t have a antlet-name definition that I can see.