Description
Describe the feature
An option in the configuration (or something) to pass in (1) a function and (2) a timeout for a given DB, where the function is called after the timeout duration continuously (that is, waits for the timeout and calls the function, in a loop, forever) and the function returns database connection credentials and the DB reconnects with those credentials.
Motivation
I want to be able to use instances of AWS Redshift's postgres-based database. That's all well and fine, you can just request credentials through their API and use them for connections. The issue is that the longest those credentials are valid is 60 minutes. I need to be able to have Redshift always connected so I can serve data from it as responses to API hits. For example, I could write a function that requests credentials from Redshift that would remain valid for 60 minutes, and specify a timeout of 59 minutes. If a reconnection fails, it could possibly default back to the old credentials/connection and restart the timeout.
So, something where I can essentially write a credentials-providing function and provide a timeout so that the DB is always connected in situations like this would be immensely helpful. I imagine it would also be useful for similar products or connection limitation schemes from cloud providers like Azure. This could be theoretically used for some niche situation where someone wants to roll between different credential sets.
Related Issues
None known