Closed
Description
It would be nice if the Pool supported rotating connection details. Our use-case would be using the hashicorp vault database secrets engine to generate postgres credentials on-the-fly. These credentials inherently have a limited life-span so when they expire we'd need to rotate them. As a work-around we were going to swap out the pool with a new pool but #290 prevents that.
One possible way to implement it, would be:
- expose a function to set the connection details
- when that function is called, all new calls to
acquire()
would return connections with the new connection details set - as connections with the old details are returned to the pool they get discarded
I could see this also being useful for fail-overs but thats not our use-case so idk
Metadata
Metadata
Assignees
Labels
No labels