Sync web site with Quarkus documentation

Author: quarkusbot

_generated-doc/3.15/config/quarkus-all-config.adoc

@@ -50060,7 +50060,7 @@ Environment variable: `+++QUARKUS_MONGODB_DNS_SERVER_PORT+++`
 endif::add-copy-button-to-env-var[]
 --
 |int
-|`53`
+|
 
 a| [[quarkus-mongodb-client_quarkus-mongodb-dns-lookup-timeout]] [.property-path]##link:#quarkus-mongodb-client_quarkus-mongodb-dns-lookup-timeout[`quarkus.mongodb.dns.lookup-timeout`]##
 

_generated-doc/3.15/config/quarkus-mongodb-client.adoc

@@ -508,7 +508,7 @@ Environment variable: `+++QUARKUS_MONGODB_DNS_SERVER_PORT+++`
 endif::add-copy-button-to-env-var[]
 --
 |int
-|`53`
+|
 
 a| [[quarkus-mongodb-client_quarkus-mongodb-dns-lookup-timeout]] [.property-path]##link:#quarkus-mongodb-client_quarkus-mongodb-dns-lookup-timeout[`quarkus.mongodb.dns.lookup-timeout`]##
 

_generated-doc/3.15/config/quarkus-mongodb-client_quarkus.mongodb.adoc

@@ -508,7 +508,7 @@ Environment variable: `+++QUARKUS_MONGODB_DNS_SERVER_PORT+++`
 endif::add-copy-button-to-env-var[]
 --
 |int
-|`53`
+|
 
 a| [[quarkus-mongodb-client_quarkus-mongodb-dns-lookup-timeout]] [.property-path]##link:#quarkus-mongodb-client_quarkus-mongodb-dns-lookup-timeout[`quarkus.mongodb.dns.lookup-timeout`]##
 

_generated-doc/3.15/infra/quarkus-maven-plugin-goals.adoc

@@ -3672,7 +3672,7 @@ a| [[quarkus-maven-plugin-goal-track-config-changes-quarkus.recorded-build-confi
 |`${basedir}/.quarkus`
 
 a| [[quarkus-maven-plugin-goal-track-config-changes-quarkus.recorded-build-config.file]] quarkus.recorded-build-config.file
-|`File`
+|`String`
 |
 
 a| [[quarkus-maven-plugin-goal-track-config-changes-repoSession]] repoSession

_versions/3.15/guides/_attributes.adoc

@@ -1,7 +1,7 @@
 // Common attributes.
 // --> No blank lines (it ends the document header)
 :project-name: Quarkus
-:quarkus-version: 3.15.4
+:quarkus-version: 3.15.5
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.8

_versions/3.15/guides/gradle-tooling.adoc

@@ -579,7 +579,7 @@ The entries are relative to the root of the generated Uber-Jar. You can specify
 By default, Quarkus will not discover CDI beans inside another module.
 
 The best way to enable CDI bean discovery for a module in a multi-module project would be to include a `META-INF/beans.xml` file,
-unless it is the main application module already configured with the quarkus-maven-plugin, in which case it will be indexed automatically.
+unless it is the main application module already configured with the `io.quarkus` Gradle plugin, in which case it will be indexed automatically.
 
 Alternatively, there is some unofficial link:https://plugins.gradle.org/search?term=jandex[Gradle Jandex plugins] that can be used instead of the `META-INF/beans.xml` file.
 

_versions/3.15/guides/rest.adoc

@@ -1597,7 +1597,7 @@ public User userPrivate() {
 }
 ----
 
-When the result the `userPublic` method is serialized, the `id` field will not be contained in the response as the `Public` view does not include it.
+When the result of the `userPublic` method is serialized, the `id` field will not be contained in the response as the `Public` view does not include it.
 The result of `userPrivate` however will include the `id` as expected when serialized.
 
 ===== Reflection-free Jackson serialization

_versions/3.15/guides/security-ldap.adoc

@@ -160,22 +160,36 @@ quarkus.security.ldap.enabled=true
 
 quarkus.security.ldap.dir-context.principal=uid=admin,ou=system
 quarkus.security.ldap.dir-context.url=ldaps://ldap.server.local <1>
+%test.quarkus.security.ldap.dir-context.url=ldap://127.0.0.1:10389 <2>
 quarkus.security.ldap.dir-context.password=secret
 
 quarkus.security.ldap.identity-mapping.rdn-identifier=uid
 quarkus.security.ldap.identity-mapping.search-base-dn=ou=Users,dc=quarkus,dc=io
 
 quarkus.security.ldap.identity-mapping.attribute-mappings."0".from=cn
-quarkus.security.ldap.identity-mapping.attribute-mappings."0".filter=(member=uid={0},ou=Users,dc=quarkus,dc=io) <2>
+quarkus.security.ldap.identity-mapping.attribute-mappings."0".filter=(member=uid={0},ou=Users,dc=quarkus,dc=io) <3>
 quarkus.security.ldap.identity-mapping.attribute-mappings."0".filter-base-dn=ou=Roles,dc=quarkus,dc=io
-
-%test.quarkus.security.ldap.dir-context.url=ldap://127.0.0.1:10389 <3>
 ----
 <1> You need to provide the URL to an LDAP server. This example requires the LDAP server to have imported link:{quarkus-blob-url}/test-framework/ldap/src/main/resources/quarkus-io.ldif[this LDIF file].
-<2> `{0}` is substituted by the `uid`.
-<3> The URL used by our test resource. Tests may leverage `LdapServerTestResource` provided by Quarkus as link:{quickstarts-blob-url}/security-ldap-quickstart/src/test/java/org/acme/elytron/security/ldap/ElytronLdapExtensionTestResources.java[we do] in the test coverage of the example application.
+<2> The URL used by our test resource. Tests may leverage `LdapServerTestResource` provided by Quarkus as link:{quickstarts-blob-url}/security-ldap-quickstart/src/test/java/org/acme/elytron/security/ldap/ElytronLdapExtensionTestResources.java[we do] in the test coverage of the example application.
+<3> `{0}` is substituted by the `uid`.
+
+The `quarkus-elytron-security-ldap` extension requires a dir-context and an identity-mapping with at least one attribute-mapping to authenticate the user and its identity.
+
+[TIP]
+====
+By default, Quarkus doesn't cache the credentials obtained from the LDAP directory.
+Every request to your service will cause an additional roundtrip to the LDAP server.
+
+It is a common practice to cache these results to improve performance, but the tradeoff is that there will be a delay before the changes in the LDAP get effective in your service.
+
+To enable the cache, set `quarkus.security.ldap.cache.enabled=true` in your configuration file.
+
+The default cache max-age is `60s`.
+It can be configured by setting `quarkus.security.ldap.cache.max-age`.
 
-The `elytron-security-ldap` extension requires a dir-context and an identity-mapping with at least one attribute-mapping to authenticate the user and its identity.
+The number of cache entries is limited by `quarkus.security.ldap.cache.size`, which defaults to `100`.
+====
 
 === Map LDAP groups to `SecurityIdentity` roles
 

_versions/3.15/guides/stylesheet/config.css

@@ -105,7 +105,7 @@ table.configuration-reference.tableblock td.tableblock > .content > :last-child
   margin-bottom: inherit;
 }
 
-input#config-search-0 {
+input[id^="config-search-"] {
   -webkit-appearance: none;
   display: block;
   width: 100%;
@@ -127,8 +127,8 @@ input#config-search-0 {
   letter-spacing: 1.5px;
 }
 
-input#config-search-0:hover,
-input#config-search-0:focus {
+input[id^="config-search-"]:hover,
+input[id^="config-search-"]:focus {
   padding: 12px 2px;
   outline: 0;
   border: 1px solid transparent;

_versions/3.15/guides/telemetry-micrometer.adoc

@@ -10,7 +10,7 @@ include::_attributes.adoc[]
 :categories: observability
 :summary: Use Micrometer to collect metrics produced by Quarkus, its extensions, and your application.
 :base-units: https://github.com/micrometer-metrics/micrometer/blob/main/micrometer-core/src/main/java/io/micrometer/core/instrument/binder/BaseUnits.java
-:concepts: https://micrometer.io/docs/concepts
+:concepts: https://docs.micrometer.io/micrometer/reference/concepts
 :topics: observability,micrometer
 :extensions: io.quarkus:quarkus-micrometer
 
@@ -186,7 +186,7 @@ For hierarchical systems that only support a flat metric name, Micrometer will f
 
 Tags can be specified when a meter is registered with a `MeterRegistry` or using a <<meter-filter,Meter Filter>>.
 
-See the Micrometer documentation for additional advice on link:{concepts}#_tag_naming[tag naming].
+See the Micrometer documentation for additional advice on link:{concepts}/naming[tag naming].
 
 IMPORTANT: Each unique combination of metric name and dimension produces a unique time series.
 Using an unbounded set of dimensional data can lead to a "cardinality explosion", an exponential increase in the creation of new time series.
@@ -277,7 +277,7 @@ Gauge.builder("jvm.threads.peak", threadBean, ThreadMXBean::getPeakThreadCount)
 <4> Associate <<define-tags,tags>> with the gauge
 <5> Register the Gauge with the MeterRegistry
 
-See link:{concepts}#_gauges[Gauges] in the Micrometer documentation for more information and examples.
+See link:{concepts}/gauges[Gauges] in the Micrometer documentation for more information and examples.
 Of note are two special cases: `TimeGauge` for measuring time, and a `MultiGauge` for reporting several criteria together.
 
 NOTE: Micrometer does not create strong references to the objects it observes by default.
@@ -334,7 +334,7 @@ void countThisMethod(){
 <1> A CDI interceptor will create and register a counter called `counted.method`
 <2> The interceptor-created counter will have the "extra" dimension tag with value "annotated"
 
-See link:{concepts}#_counters[Counters] in the Micrometer documentation for more information and examples, including the less common `FunctionCounter` that can be used to measure the result returned by an always increasing function.
+See link:{concepts}/counters[Counters] in the Micrometer documentation for more information and examples, including the less common `FunctionCounter` that can be used to measure the result returned by an always increasing function.
 
 When should you use a counter?
 Use a counter if you are doing something that can not be either timed or summarized.
@@ -476,7 +476,7 @@ sample.stop(registry.timer("my.timer", "response", response.status())); // <3>
 ==== Histograms and percentiles
 
 Both timers and distribution summaries can be configured to emit additional statistics, like histogram data, precomputed percentiles, or service level objective (SLO) boundaries.
-See link:{concepts}#_timers[Timers] and link:{concepts}#_distribution_summaries[Distribution Summaries] in the Micrometer documentation for more information and examples, including memory footprint estimation for both types.
+See link:{concepts}/timers[Timers] and link:{concepts}/distribution-summaries[Distribution Summaries] in the Micrometer documentation for more information and examples, including memory footprint estimation for both types.
 
 [IMPORTANT]
 ====