New TLS registry: How to configure certificate reload period?

[sdavids]

Describe the bug

https://quarkus.io/guides/tls-registry-reference

There is no example of how to configure the certificate reload period.

Expected behavior

There is a migration example for:

quarkus.http.ssl.certificate.files=cert.pem
quarkus.http.ssl.certificate.key-files=key.pem
quarkus.http.ssl.certificate.reload-period=30s

⇓

quarkus.tls.key-store.pem.0.cert=cert.pem
quarkus.tls.key-store.pem.0.key=key.pem
??? quarkus.tls.key-store.pem.0.reload-period=30s ???

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

3.12.1

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot[bot]]

/cc @radcortez (config)

[geoand]

cc @cescoffier

[cescoffier]

That feature has not been released yet, but you can see the "next-to-be" documentation on: https://quarkus.io/version/main/guides/tls-registry-reference#reloading-certificates

Note that the TLS registry, unlike the previous approach let you implement your own reloader (so not only periodic)