-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Allow TLS certificate reloading for the HTTP server #38608
Conversation
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.
Good stuff!
I added a couple questions
...p/runtime/src/main/java/io/quarkus/vertx/http/runtime/options/TlsCertificateReloadUtils.java
Outdated
Show resolved
Hide resolved
...p/runtime/src/main/java/io/quarkus/vertx/http/runtime/options/TlsCertificateReloadUtils.java
Outdated
Show resolved
Hide resolved
...p/runtime/src/main/java/io/quarkus/vertx/http/runtime/options/TlsCertificateReloadUtils.java
Outdated
Show resolved
Hide resolved
This comment has been minimized.
This comment has been minimized.
🙈 The PR is closed and the preview is expired. |
...nsions/vertx-http/runtime/src/main/java/io/quarkus/vertx/http/runtime/CertificateConfig.java
Show resolved
Hide resolved
Key store, trust store and certificate files can be reloaded periodically. The period is configured using the `quarkus.http.ssl.certificate.reload-period` property. The files are reloaded from the same location as they were initially loaded from. If there is no content change, the reloading is a no-op. It the reloading fails, the server will continue to use the previous certificates.
1beea62
to
6ab3ced
Compare
Status for workflow
|
Status for workflow
|
In the end, it was decided not to backport it. |
If we backport this one, we will also need this one: #39026 |
Key store, trust store and certificate files can be reloaded periodically.
The period is configured using the
quarkus.http.ssl.certificate.reload-period
property.The files are reloaded from the same location as they were initially loaded from.
If there is no content change, the reloading is a no-op.
It the reloading fails, the server will continue to use the previous certificates.
Fix #15926.