check if pool exists

DOH! You're right, my bad.

 

 

In the example it is necessary to use it twice, once to validate the node exists, and once to actually send the traffic there. If it doesn't exist, load balance the traffic to pool myPool

 

 

I think I remember reading on a thread that the node doesn't technically have to exist in the configuration to assign it, so this might be a customer requirement. Also, since the information is dynamic, it might not be formatted correctly and will thus throw an error.