Allow definiting Status, enabled or disabled, in pool attachment about terraform-provider-bigip HOT 4 CLOSED

@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.

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

from terraform-provider-bigip.

Is this being looked into at all? This type of lacking support makes it impossible to manage the F5 with a tool like Terraform beyond initial configuration.
When I choose 'user-up' or 'user-down' for the node, it either sets the node state to forced offline or disabled. Neither of them show the node as enabled.

Even if that worked, you can't only rely on this for gracefully draining connections since sometimes a node is part of multiple pools and disabling an entire node is not an option. Why is there no way to configure state through the pool membership?

from terraform-provider-bigip.

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.)

from terraform-provider-bigip.

Hi, closing this request now.
Please re-open if required or send an email to [email protected]. Thanks!

from terraform-provider-bigip.