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
In resource outscale_load_balancer_vms, backend_vm_ids is a List. When there are changes to this list, there is a replacement of the resource, which trigger the Deregister of all backends, and then the register of all backends. This can disrupt the service in entirety when adding just one host.
Furthermore, because it's a list of VM IDs, the ID is not known before the VM is created, so there is a certain time between De-register and re-registering for backends that were there before.
Attempted Solutions
Creating one attachment resource by VM is tricky, because you have to map each attachment to a VM, and you cannot use the instance id in the for_each label.
Proposal
Add a differential update feature for the outscale_load_balancer_vms ressource, that works by reading the existing backends, filtering them with the "expected" backends, and then calculating a differential update (Register new backends, Deregister old backends), avoiding changes for backends that did not move, or backends that are not managed by this resource.
References
None known
The text was updated successfully, but these errors were encountered:
Current Terraform Version
Use-cases
In resource outscale_load_balancer_vms, backend_vm_ids is a List. When there are changes to this list, there is a replacement of the resource, which trigger the Deregister of all backends, and then the register of all backends. This can disrupt the service in entirety when adding just one host.
Furthermore, because it's a list of VM IDs, the ID is not known before the VM is created, so there is a certain time between De-register and re-registering for backends that were there before.
Attempted Solutions
Creating one attachment resource by VM is tricky, because you have to map each attachment to a VM, and you cannot use the instance id in the for_each label.
Proposal
Add a differential update feature for the outscale_load_balancer_vms ressource, that works by reading the existing backends, filtering them with the "expected" backends, and then calculating a differential update (Register new backends, Deregister old backends), avoiding changes for backends that did not move, or backends that are not managed by this resource.
References
None known
The text was updated successfully, but these errors were encountered: