r/ovh_iploadbalancing_tcp_frontend: new resource

[yanndegat]

No description provided.

[yanndegat]

hi @goblain

i'm adding this new resource
wonder if you could had a glimpse at it & review it ?

one major point: the refresh mechanism which is missing the farm/farm_server resources.
i'll make another PR to fix these too

[goblain]

will look in a moment, btw. I actually have a refresh that I use, but no tests around it (https://github.com/goblain/terraform-provider-ovh/blob/workinprogress/ovh/resource_ovh_iploadbalancing_refresh.go)

[goblain]

I do not specially like the idea that resource update triggers immediate refresh within it's change logic. If we have more then one change, it will add extreme delays to the operation. As I hinted above, I would lean more to having a refresh resource that can be used after all the changes were implemented, to trigger a single reload of full new config. This also helps to avoid application of partial state to the OVH loadbalancer, as it's then called only after full state is configured.

resource "ovh_iploadbalancing_refresh" "ingress" {
  service_name = "${data.ovh_iploadbalancing.lb.id}"
  keepers = [
    "${ovh_iploadbalancing_tcp_farm_server.ingress-80-compute-blue.*.address}",
    "${ovh_iploadbalancing_tcp_farm_server.ingress-443-compute-blue.*.address}"
  ]
}

is how I use it in my case, to trigger refresh after resources were changed

[yanndegat]

you're abs. right

then we'll try to work on your refresh resource
don't you mind to make a PR, i'll merge it and try to add the missing features ?

[goblain]

few notes on first pass on my side

[goblain]

as mentioned before, I would consider moving it to separate refresh resource

[yanndegat]

thanks a lot for your review