From 7f56ac6531011d759a32e5749626651efb17e98a Mon Sep 17 00:00:00 2001 From: Peter Palaga Date: Wed, 16 Oct 2024 12:39:14 +0200 Subject: [PATCH] Use the correct event type CertificateUpdatedEvent in TLS Registry reference --- docs/src/main/asciidoc/tls-registry-reference.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/tls-registry-reference.adoc b/docs/src/main/asciidoc/tls-registry-reference.adoc index 4024783fe2e8a..86f9a23cc39b6 100644 --- a/docs/src/main/asciidoc/tls-registry-reference.adoc +++ b/docs/src/main/asciidoc/tls-registry-reference.adoc @@ -675,7 +675,7 @@ quarkus.tls.http.key-store.pem.0.cert=tls.crt quarkus.tls.http.key-store.pem.0.key=tls.key ---- -IMPORTANT: Impacted server and client may need to listen to the `CertificateReloadedEvent` to apply the new certificates. +IMPORTANT: Impacted server and client may need to listen to the `CertificateUpdatedEvent` to apply the new certificates. This is automatically done for the Quarkus HTTP server, including the management interface if it is enabled. ifndef::no-kubernetes-secrets-or-cert-manager[]