-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCDA Support #1259
Comments
Hello, Sorry, but VCDA is not part of this provider. This project is for VCD provider. |
@lvirbalas Will a separate provider be developed for VCDA? Is that something on a roadmap? |
@Nagte502 please refer here: https://github.com/vmware/terraform-provider-vcda |
We've looked at this provider, but this provider is used for deploying the VCDA appliance itself. Not manage resources in it. But based on your response I don't think there are any plans for this to be developed. |
This conclusion cannot be drawn from this discussion :) Better ask in terraform-provider-vcda project. |
Hi!
We are currently working with terraform on VCD and are faced with a challenge. Within our VCD environment, we use VCDA for disaster recovery and workload migrations. This creates a unique challenge in which VCDA moves a workload away, but the terraform state dicates that a the workload should be present in a specific location. When applying the terraform state, terraform will recreate the workload back where it use to be (a duplicate). Even when migrating back and forth, the machines ID's will have been updated, triggering a destroy and recreate action.
Is VCDA support somewhere close on the roadmap or will this be developed at all?
(I have seen a VCDA provider, but only for deploying VCDA, not managing workloads with it?)
What is the best way of dealing with this challenge without VCDA support in this module?
Thank you for the response in advance!
The text was updated successfully, but these errors were encountered: