Sync documentation of main branch

Author: actions-user

_generated-doc/main/config/all-configuration-groups-generated-doc/io.quarkus.redis.runtime.client.config.RedisClientConfig

@@ -0,0 +1 @@
+[{"configDocKey":{"type":"boolean","key":"quarkus.tls.lets-encrypt.enabled","additionalKeys":[],"configDoc":"Set to `true` to enable let's encrypt support.","withinAMap":false,"defaultValue":"false","javaDocSiteLink":"","docMapKey":"enabled","configPhase":"BUILD_TIME","acceptedValues":null,"optional":false,"list":false,"withinAConfigGroup":false,"topLevelGrouping":"quarkus.tls.lets-encrypt","since":null,"environmentVariable":"QUARKUS_TLS_LETS_ENCRYPT_ENABLED","enum":false}}]

_generated-doc/main/config/all-configuration-roots-generated-doc/io.quarkus.redis.runtime.client.config.RedisConfig

@@ -0,0 +1 @@
+io.quarkus.tls.LetsEncryptBuildTimeConfig

_generated-doc/main/config/all-configuration-roots-generated-doc/io.quarkus.tls.LetsEncryptBuildTimeConfig

@@ -1857,6 +1857,10 @@ _No Javadoc found_
 
 _No Javadoc found_
 
+`boolean classes` 
+
+_No Javadoc found_
+
 `boolean constructors` 
 
 _No Javadoc found_

_generated-doc/main/config/extensions-configuration-roots-list/quarkus-tls.adoc/io.quarkus.tls.LetsEncryptBuildTimeConfig

@@ -65976,9 +65976,7 @@ a| [[quarkus-redis-client_quarkus-redis-max-pool-size]]`link:#quarkus-redis-clie
 
 [.description]
 --
-The maximum size of the connection pool. When working with cluster or sentinel.
-
-This value should be at least the total number of cluster member (or number of sentinels {plus} 1)
+The maximum size of the connection pool. When working with cluster or sentinel, this value should be at least the total number of cluster members (or number of sentinels {plus} 1)
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS_MAX_POOL_SIZE+++[]
@@ -66534,9 +66532,7 @@ a| [[quarkus-redis-client_quarkus-redis-redis-client-name-max-pool-size]]`link:#
 
 [.description]
 --
-The maximum size of the connection pool. When working with cluster or sentinel.
-
-This value should be at least the total number of cluster member (or number of sentinels {plus} 1)
+The maximum size of the connection pool. When working with cluster or sentinel, this value should be at least the total number of cluster members (or number of sentinels {plus} 1)
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS__REDIS_CLIENT_NAME__MAX_POOL_SIZE+++[]
@@ -72238,6 +72234,23 @@ endif::add-copy-button-to-env-var[]
 |
 
 
+a|icon:lock[title=Fixed at build time] [[quarkus-tls-registry_quarkus-tls-lets-encrypt-enabled]]`link:#quarkus-tls-registry_quarkus-tls-lets-encrypt-enabled[quarkus.tls.lets-encrypt.enabled]`
+
+
+[.description]
+--
+Set to `true` to enable let's encrypt support.
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_TLS_LETS_ENCRYPT_ENABLED+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_TLS_LETS_ENCRYPT_ENABLED+++`
+endif::add-copy-button-to-env-var[]
+--|boolean 
+|`false`
+
+
 h|[[quarkus-tls-registry_quarkus-tls-default-certificate-config-the-default-tls-bucket-configuration]]link:#quarkus-tls-registry_quarkus-tls-default-certificate-config-the-default-tls-bucket-configuration[The default TLS bucket configuration]
 This configuration section is optional
 h|Type

_generated-doc/main/config/quarkus-all-build-items.adoc

@@ -285,7 +285,7 @@ a| [[quarkus-maven-plugin-goal-build-bootstrapid]]`link:#quarkus-maven-plugin-go
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 
@@ -1196,7 +1196,7 @@ a| [[quarkus-maven-plugin-goal-deploy-bootstrapid]]`link:#quarkus-maven-plugin-g
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 
@@ -1760,7 +1760,7 @@ a| [[quarkus-maven-plugin-goal-generate-code-bootstrapid]]`link:#quarkus-maven-p
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 
@@ -1931,7 +1931,7 @@ a| [[quarkus-maven-plugin-goal-generate-code-tests-bootstrapid]]`link:#quarkus-m
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 
@@ -2230,7 +2230,7 @@ a| [[quarkus-maven-plugin-goal-image-build-bootstrapid]]`link:#quarkus-maven-plu
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 
@@ -2473,7 +2473,7 @@ a| [[quarkus-maven-plugin-goal-image-push-bootstrapid]]`link:#quarkus-maven-plug
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 
@@ -3118,7 +3118,7 @@ a| [[quarkus-maven-plugin-goal-native-image-agent-bootstrapid]]`link:#quarkus-ma
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 
@@ -3269,7 +3269,7 @@ a| [[quarkus-maven-plugin-goal-prepare-bootstrapid]]`link:#quarkus-maven-plugin-
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 
@@ -3440,7 +3440,7 @@ a| [[quarkus-maven-plugin-goal-prepare-tests-bootstrapid]]`link:#quarkus-maven-p
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 
@@ -4140,7 +4140,7 @@ a| [[quarkus-maven-plugin-goal-run-bootstrapid]]`link:#quarkus-maven-plugin-goal
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 
@@ -4626,7 +4626,7 @@ a| [[quarkus-maven-plugin-goal-track-config-changes-bootstrapid]]`link:#quarkus-
 
 [.description]
 --
-Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
+Application bootstrap provider ID. This parameter is not supposed to be configured by the user. To be able to re-use an application bootstrapped in one phase in a later phase, there needs to be a way to identify the correct instance of the bootstrapped application (in case there are more than one) in each Mojo. A bootstrap ID serves this purpose. This parameter is set in DevMojo invoking generate-code and generate-code-tests goals. If this parameter is not configured, a Mojo execution ID will be used as the bootstrap ID.
 --|String 
 |
 

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

@@ -164,9 +164,7 @@ a| [[quarkus-redis-client-config-redis-config_quarkus-redis-max-pool-size]]`link
 
 [.description]
 --
-The maximum size of the connection pool. When working with cluster or sentinel.
-
-This value should be at least the total number of cluster member (or number of sentinels {plus} 1)
+The maximum size of the connection pool. When working with cluster or sentinel, this value should be at least the total number of cluster members (or number of sentinels {plus} 1)
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS_MAX_POOL_SIZE+++[]
@@ -534,9 +532,7 @@ a| [[quarkus-redis-client-config-redis-config_quarkus-redis-redis-client-name-ma
 
 [.description]
 --
-The maximum size of the connection pool. When working with cluster or sentinel.
-
-This value should be at least the total number of cluster member (or number of sentinels {plus} 1)
+The maximum size of the connection pool. When working with cluster or sentinel, this value should be at least the total number of cluster members (or number of sentinels {plus} 1)
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS__REDIS_CLIENT_NAME__MAX_POOL_SIZE+++[]

_generated-doc/main/config/quarkus-maven-plugin-goals.adoc

@@ -164,9 +164,7 @@ a| [[quarkus-redis-config-group-client-config-redis-client-config_quarkus-redis-
 
 [.description]
 --
-The maximum size of the connection pool. When working with cluster or sentinel.
-
-This value should be at least the total number of cluster member (or number of sentinels {plus} 1)
+The maximum size of the connection pool. When working with cluster or sentinel, this value should be at least the total number of cluster members (or number of sentinels {plus} 1)
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS_MAX_POOL_SIZE+++[]
@@ -534,9 +532,7 @@ a| [[quarkus-redis-config-group-client-config-redis-client-config_quarkus-redis-
 
 [.description]
 --
-The maximum size of the connection pool. When working with cluster or sentinel.
-
-This value should be at least the total number of cluster member (or number of sentinels {plus} 1)
+The maximum size of the connection pool. When working with cluster or sentinel, this value should be at least the total number of cluster members (or number of sentinels {plus} 1)
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS__REDIS_CLIENT_NAME__MAX_POOL_SIZE+++[]

_generated-doc/main/config/quarkus-redis-client-config-redis-config.adoc

@@ -316,9 +316,7 @@ a| [[quarkus-redis-general-config-items_quarkus-redis-max-pool-size]]`link:#quar
 
 [.description]
 --
-The maximum size of the connection pool. When working with cluster or sentinel.
-
-This value should be at least the total number of cluster member (or number of sentinels {plus} 1)
+The maximum size of the connection pool. When working with cluster or sentinel, this value should be at least the total number of cluster members (or number of sentinels {plus} 1)
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS_MAX_POOL_SIZE+++[]
@@ -874,9 +872,7 @@ a| [[quarkus-redis-general-config-items_quarkus-redis-redis-client-name-max-pool
 
 [.description]
 --
-The maximum size of the connection pool. When working with cluster or sentinel.
-
-This value should be at least the total number of cluster member (or number of sentinels {plus} 1)
+The maximum size of the connection pool. When working with cluster or sentinel, this value should be at least the total number of cluster members (or number of sentinels {plus} 1)
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS__REDIS_CLIENT_NAME__MAX_POOL_SIZE+++[]