12-Jul-202110:36 - last edited on 22-Nov-202215:07 by JimmyPackets
We are currently using a powershell script to move pool members in and out of pools during deployment. We have one site that the connection can sometimes remain open for a long period of time. We'd like to set a limit on how long it will wait for a connection to close before forcing the connection closed no matter how many connections remain open. We are using the code below to disable the F5 pool member.
What I'd like to do is have it wait for a variable amount of time ($timetowait) (or something like that) that can be passed down through the CI/CD pipeline. So then our developers can input how much time, in minutes, they want to wait for the nodes to clear. So for example, if they enter 10 mins, if the pool still has connections after 10 mins, it will stop waiting and close all connections to that node.
I've dug through the documentation but I'm not seeing anything along these lines.
This way the powershell script will complete successfully and won't fail out the CI/CD pipeline process. And then we can continue on with the next steps.