-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Pause connection requests after certificate expires until refresh completes. #1600
Conversation
6af043a
to
901558d
Compare
d6ccb7e
to
9968302
Compare
901558d
to
f885230
Compare
17d7d36
to
aec18df
Compare
aec18df
to
d727280
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this counts as a feature as we're changing how refresh is done.
I know we've talked about it, but can you make a succinct case why we need this change? It feels like an edge case for when we're in a CPU throttled context, which we need to address more directly with #992.
Converting to draft until we decide to move forward. |
8735aea
to
8eba0b2
Compare
60e5344
to
c0a79a2
Compare
8eba0b2
to
051b407
Compare
d52c0f4
to
9d12ed4
Compare
051b407
to
a94f358
Compare
When the application attempts to create a database connection, and the certificate or auth token has expired,
pause until the certificate and token are refreshed. If the token is not refreshed before the timeout, throw
an exception because the connection attempt failed.