This was done because if a catalog item version is no longer available, the update function returns a 404 error. However, the blueprint version still exists and contains all the useful information we need to update a deployment.
We had an issue where an already deployment resource where no longer terraform compliant if a catalog item version was no longer available.
Also commented a line in the cloud_account_vsphere example.
This was done because if a catalog item version is no longer available, the update function returns a 404 error. However, the blueprint version still exists and contains all the useful information we need to update a deployment.
We had an issue where an already deployment resource where no longer terraform compliant if a catalog item version was no longer available.
Also commented a line in the cloud_account_vsphere example.
Signed-off-by: an2ane antoine.berlon@gmail.com