search

RavinderReddyF5 / terraform-provider-bigip-version0.12

Terraform resources that can configure F5 BIGIP products
Mozilla Public License 2.0
0 stars 0 forks source link

Allow definiting Status, enabled or disabled, in pool attachment #145

Open RavinderReddyF5 opened 4 years ago

RavinderReddyF5 commented 4 years ago

Issue by DavidGamba Thursday Jun 06, 2019 at 21:53 GMT Originally opened as https://github.com/terraform-providers/terraform-provider-bigip/issues/114

Currently, there is no way to manage pool member status through Terraform.

I set the status to disabled when I am migrating nodes and want the connections to gracefully drain before removing them from the pool.

I am assuming the place to do this would be the pool attachment resource.

RavinderReddyF5 commented 4 years ago

Comment by earchibald-lv Monday Dec 16, 2019 at 22:07 GMT

I tried setting state = "user-down" on the bigip_ltm_node to see if it would affect things.

If I only create the node without attaching it to a pool, the node is properly set to disabled.

However, if I specify the node and attach it to a pool, the node ignores the state parameter and is up (even though Terraform state shows state as user-down.)

RavinderReddyF5 commented 4 years ago

Comment by RavinderReddyF5 Tuesday Dec 17, 2019 at 11:53 GMT

@earchibald-lv we tried same scenario manually and observed below things.

when attaching any ltm node to a ltm pool, bigip will not consider current state of node.

we have to explicitly set node state as shown below snapshot.

image

image

we can add node_status attribute in "pool attachment resource" which user can add explicitly based on the node status.