feat: make tls certificates/keys reloadable (part 1) #3335
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Part 1 of implementation for #3255
This patch caches TLS
ServerConfig
in a mutable container to make it possible to update by other threads.TlsAcceptor
is a lightweight container ofServerConfig
so it's OK to create for each connnection.This patch also includes a file system watcher to detect file change of certificates/keys and reload them as needed.
Checklist
Refer to a related PR or issue link (optional)