Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add support for lazy certificate refresh #298

Open
jackwotherspoon opened this issue Apr 11, 2024 · 0 comments
Open

Add support for lazy certificate refresh #298

jackwotherspoon opened this issue Apr 11, 2024 · 0 comments
Assignees
@jackwotherspoon
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@jackwotherspoon
Copy link
Collaborator

In serverless environments, when the CPU is throttled, the Python Connector will sometimes fail to refresh the certificate and time out.

This is a feature request to allow callers to opt-in to a lazy refresh strategy, where no background tasks run and the cert is refreshed as needed.

Related to #297
@jackwotherspoon jackwotherspoon added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Apr 11, 2024
@jackwotherspoon jackwotherspoon self-assigned this Apr 11, 2024
@jackwotherspoon jackwotherspoon mentioned this issue Apr 11, 2024
Open
@nprime496 nprime496 mentioned this issue Apr 13, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jackwotherspoon jackwotherspoon

Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jackwotherspoon