Sync documentation of main branch

Author: actions-user

_data/versioned/main/index/quarkus.yaml

@@ -5,7 +5,7 @@ types:
   - title: Authorization of web endpoints
     filename: security-authorize-web-endpoints-reference.adoc
     summary: Quarkus has an integrated pluggable web security layer.
-    categories: "web, security"
+    categories: "security, web"
     id: security-authorize-web-endpoints-reference
     type: reference
     url: /guides/security-authorize-web-endpoints-reference
@@ -131,14 +131,14 @@ types:
   - title: Authentication mechanisms in Quarkus
     filename: security-authentication-mechanisms-concept.adoc
     summary: "The Quarkus Security framework supports multiple authentication mechanisms, which you can use to secure your applications."
-    categories: "web, security"
+    categories: "security, web"
     id: security-authentication-mechanisms-concept
     type: concepts
     url: /guides/security-authentication-mechanisms-concept
   - title: Basic authentication
     filename: security-basic-authentication-concept.adoc
     summary: HTTP Basic authentication is one of the least resource-demanding techniques that enforce access controls to web resources.
-    categories: "web, security"
+    categories: "security, web"
     id: security-basic-authentication-concept
     type: concepts
     url: /guides/security-basic-authentication-concept
@@ -152,21 +152,21 @@ types:
   - title: OpenID Connect (OIDC) Bearer authentication
     filename: security-oidc-bearer-token-authentication-concept.adoc
     summary: Secure HTTP access to Jakarta REST (formerly known as JAX-RS) endpoints in your application with Bearer authentication by using the Quarkus OpenID Connect (OIDC) extension.
-    categories: "web, security"
+    categories: "security, web"
     id: security-oidc-bearer-token-authentication-concept
     type: concepts
     url: /guides/security-oidc-bearer-token-authentication-concept
   - title: OpenID Connect authorization code flow mechanism for protecting web applications
     filename: security-oidc-code-flow-authentication-concept.adoc
     summary: "To protect your web applications, you can use the authorization code flow mechanism provided by the Quarkus OpenID Connect (OIDC) extension."
-    categories: "web, security"
+    categories: "security, web"
     id: security-oidc-code-flow-authentication-concept
     type: concepts
     url: /guides/security-oidc-code-flow-authentication-concept
   - title: Proactive authentication
     filename: security-proactive-authentication-concept.adoc
     summary: Proactive authentication is enabled in Quarkus by default.
-    categories: "web, security"
+    categories: "security, web"
     id: security-proactive-authentication-concept
     type: concepts
     url: /guides/security-proactive-authentication-concept
@@ -230,7 +230,7 @@ types:
   - title: Building a Native Executable
     filename: building-native-image.adoc
     summary: Build native executables with GraalVM or Mandrel.
-    categories: "native, getting-started"
+    categories: "getting-started, native"
     type: tutorial
     url: /guides/building-native-image
   - title: Collect metrics using Micrometer
@@ -243,7 +243,7 @@ types:
   - title: Configure data sources in Quarkus
     filename: datasource.adoc
     summary: Use a unified configuration model to define datasources for Java Database Connectivity (JDBC) and Reactive drivers.
-    categories: "reactive, getting-started, data"
+    categories: "getting-started, data, reactive"
     id: datasources
     type: tutorial
     url: /guides/datasource
@@ -276,7 +276,7 @@ types:
   - title: Protect a web application by using OpenID Connect (OIDC) authorization code flow
     filename: security-oidc-code-flow-authentication-tutorial.adoc
     summary: "With the Quarkus OpenID Connect (OIDC) extension, you can protect application HTTP endpoints by using the OIDC Authorization Code Flow mechanism."
-    categories: "web, security"
+    categories: "security, web"
     id: security-oidc-code-flow-authentication-tutorial
     type: tutorial
     url: /guides/security-oidc-code-flow-authentication-tutorial
@@ -484,7 +484,7 @@ types:
   - title: Deploying on OpenShift
     filename: deploying-to-openshift.adoc
     summary: This guide covers how to deploy a native application on OpenShift.
-    categories: "native, cloud"
+    categories: "cloud, native"
     id: deploy-openshift
     type: guide
     url: /guides/deploying-to-openshift
@@ -726,7 +726,7 @@ types:
     url: /guides/grpc-service-implementation
   - title: Introduction to Contexts and Dependency Injection (CDI)
     filename: cdi.adoc
-    summary: "Quarkus DI solution is based on the [Contexts and Dependency Injection for Java 2.0](https://docs.jboss.org/cdi/spec/2.0/cdi-spec) specification."
+    summary: "Quarkus DI solution is based on the [Jakarta Contexts and Dependency Injection 4.0](https://jakarta.ee/specifications/cdi/4.0/jakarta-cdi-spec-4.0.html) specification."
     categories: core
     type: guide
     url: /guides/cdi
@@ -751,7 +751,7 @@ types:
   - title: Kubernetes extension
     filename: deploying-to-kubernetes.adoc
     summary: This guide covers how to deploy a native application on Kubernetes.
-    categories: "native, cloud"
+    categories: "cloud, native"
     id: deploy-kubernetes
     type: guide
     url: /guides/deploying-to-kubernetes
@@ -879,14 +879,14 @@ types:
   - title: Quarkus and Gradle
     filename: gradle-tooling.adoc
     summary: Develop and build your Quarkus application with Gradle
-    categories: "native, tooling"
+    categories: "tooling, native"
     id: gradle-tooling
     type: guide
     url: /guides/gradle-tooling
   - title: Quarkus and Maven
     filename: maven-tooling.adoc
     summary: Develop and build your Quarkus application with Maven
-    categories: "native, tooling"
+    categories: "tooling, native"
     id: maven-tooling
     type: guide
     url: /guides/maven-tooling
@@ -984,7 +984,7 @@ types:
   - title: SmallRye Fault Tolerance
     filename: smallrye-fault-tolerance.adoc
     summary: This guide demonstrates how your Quarkus application can utilize the SmallRye Fault Tolerance specification through the SmallRye Fault Tolerance extension.
-    categories: "web, observability"
+    categories: "observability, web"
     type: guide
     url: /guides/smallrye-fault-tolerance
   - title: SmallRye GraphQL
@@ -1014,14 +1014,14 @@ types:
   - title: Testing Your Application
     filename: getting-started-testing.adoc
     summary: "This guide covers testing in JVM mode, native mode, and injection of resources into tests"
-    categories: "core, native, tooling"
+    categories: "core, tooling, native"
     id: testing
     type: guide
     url: /guides/getting-started-testing
   - title: Tips for writing native applications
     filename: writing-native-applications-tips.adoc
     summary: This guide is a collection of tips to help you solve the problems you encounter when compiling applications to native executable.
-    categories: "writing-extensions, core, native"
+    categories: "core, writing-extensions, native"
     type: guide
     url: /guides/writing-native-applications-tips
   - title: Update projects to the latest version of Quarkus
@@ -1157,7 +1157,7 @@ types:
   - title: Using SSL With Native Executables
     filename: native-and-ssl.adoc
     summary: "In this guide, we will discuss how you can get your native images to support SSL, as native images don't support it out of the box."
-    categories: "core, native, security"
+    categories: "core, security, native"
     type: guide
     url: /guides/native-and-ssl
   - title: Using Security with .properties File
@@ -1264,7 +1264,7 @@ types:
   - title: Validation with Hibernate Validator
     filename: validation.adoc
     summary: This guide covers how to use Hibernate Validator/Bean Validation in your REST services.
-    categories: "web, data"
+    categories: "data, web"
     type: guide
     url: /guides/validation
   - title: Writing JSON REST Services

_generated-doc/main/config/all-configuration-groups-generated-doc/io.quarkus.deployment.pkg.NativeConfig.BuilderImageConfig

@@ -0,0 +1 @@
+[{"configDocKey":{"type":"string","key":"","configDoc":"The docker image to use to do the image build. It can be one of `graalvm`, `mandrel`, or the full image path, e.g. `quay.io/quarkus/ubi-quarkus-mandrel-builder-image:22.3-java17`.","withinAMap":false,"defaultValue":"mandrel","javaDocSiteLink":"","docMapKey":"image","configPhase":"BUILD_TIME","acceptedValues":null,"optional":false,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"io.quarkus.deployment.pkg.NativeConfig.ImagePullStrategy","key":".pull","configDoc":"The strategy for pulling the builder image during the build. \nDefaults to 'always', which will always pull the most up-to-date image; useful to keep up with fixes when a (floating) tag is updated. \nUse 'missing' to only pull if there is no image locally; useful on development environments where building with out-of-date images is acceptable and bandwidth may be limited. \nUse 'never' to fail the build if there is no image locally.","withinAMap":false,"defaultValue":"always","javaDocSiteLink":"","docMapKey":"pull","configPhase":"BUILD_TIME","acceptedValues":["`always`","`missing`","`never`"],"optional":false,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":true}}]

_generated-doc/main/config/all-configuration-groups-generated-doc/io.quarkus.smallrye.reactivemessaging.amqp.deployment.AmqpDevServicesBuildTimeConfig

@@ -1 +1 @@
-[{"configDocKey":{"type":"java.lang.Boolean","key":".enabled","configDoc":"If Dev Services for AMQP has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For AMQP, Dev Services starts a broker unless `amqp-host` or `amqp-port` are set or if all the Reactive Messaging AMQP channel are configured with `host` or `port`.","withinAMap":false,"defaultValue":"","javaDocSiteLink":"","docMapKey":"enabled","configPhase":"BUILD_TIME","acceptedValues":null,"optional":true,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"java.lang.Integer","key":".port","configDoc":"Optional fixed port the dev service will listen to. \nIf not defined, the port will be chosen randomly.","withinAMap":false,"defaultValue":"","javaDocSiteLink":"","docMapKey":"port","configPhase":"BUILD_TIME","acceptedValues":null,"optional":true,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"string","key":".image-name","configDoc":"The image to use. Note that only ActiveMQ Artemis images are supported. Specifically, the image repository must end with `artemiscloud/activemq-artemis-broker`. Check https://quay.io/repository/artemiscloud/activemq-artemis-broker to find the available versions.","withinAMap":false,"defaultValue":"quay.io/artemiscloud/activemq-artemis-broker:1.0.11","javaDocSiteLink":"","docMapKey":"image-name","configPhase":"BUILD_TIME","acceptedValues":null,"optional":false,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"string","key":".extra-args","configDoc":"The value of the `AMQ_EXTRA_ARGS` environment variable to pass to the container.","withinAMap":false,"defaultValue":"--no-autotune --mapped --no-fsync --relax-jolokia --http-host 0.0.0.0","javaDocSiteLink":"","docMapKey":"extra-args","configPhase":"BUILD_TIME","acceptedValues":null,"optional":false,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"boolean","key":".shared","configDoc":"Indicates if the AMQP broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for AMQP starts a new container. \nThe discovery uses the `quarkus-dev-service-amqp` label. The value is configured using the `service-name` property. \nContainer sharing is only used in dev mode.","withinAMap":false,"defaultValue":"true","javaDocSiteLink":"","docMapKey":"shared","configPhase":"BUILD_TIME","acceptedValues":null,"optional":false,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"string","key":".service-name","configDoc":"The value of the `quarkus-dev-service-aqmp` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for AMQP looks for a container with the `quarkus-dev-service-amqp` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-amqp` label set to the specified value. \nThis property is used when you need multiple shared AMQP brokers.","withinAMap":false,"defaultValue":"amqp","javaDocSiteLink":"","docMapKey":"service-name","configPhase":"BUILD_TIME","acceptedValues":null,"optional":false,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}}]
+[{"configDocKey":{"type":"java.lang.Boolean","key":".enabled","configDoc":"If Dev Services for AMQP has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For AMQP, Dev Services starts a broker unless `amqp-host` or `amqp-port` are set or if all the Reactive Messaging AMQP channel are configured with `host` or `port`.","withinAMap":false,"defaultValue":"","javaDocSiteLink":"","docMapKey":"enabled","configPhase":"BUILD_TIME","acceptedValues":null,"optional":true,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"java.lang.Integer","key":".port","configDoc":"Optional fixed port the dev service will listen to. \nIf not defined, the port will be chosen randomly.","withinAMap":false,"defaultValue":"","javaDocSiteLink":"","docMapKey":"port","configPhase":"BUILD_TIME","acceptedValues":null,"optional":true,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"string","key":".image-name","configDoc":"The image to use. Note that only ActiveMQ Artemis images are supported. Specifically, the image repository must end with `artemiscloud/activemq-artemis-broker`. Check the link:https://quay.io/repository/artemiscloud/activemq-artemis-broker[activemq-artemis-broker on Quay page] to find the available versions.","withinAMap":false,"defaultValue":"quay.io/artemiscloud/activemq-artemis-broker:1.0.18","javaDocSiteLink":"","docMapKey":"image-name","configPhase":"BUILD_TIME","acceptedValues":null,"optional":false,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"string","key":".extra-args","configDoc":"The value of the `AMQ_EXTRA_ARGS` environment variable to pass to the container.","withinAMap":false,"defaultValue":"--no-autotune --mapped --no-fsync --relax-jolokia --http-host 0.0.0.0","javaDocSiteLink":"","docMapKey":"extra-args","configPhase":"BUILD_TIME","acceptedValues":null,"optional":false,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"boolean","key":".shared","configDoc":"Indicates if the AMQP broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for AMQP starts a new container. \nThe discovery uses the `quarkus-dev-service-amqp` label. The value is configured using the `service-name` property. \nContainer sharing is only used in dev mode.","withinAMap":false,"defaultValue":"true","javaDocSiteLink":"","docMapKey":"shared","configPhase":"BUILD_TIME","acceptedValues":null,"optional":false,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}},{"configDocKey":{"type":"string","key":".service-name","configDoc":"The value of the `quarkus-dev-service-aqmp` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for AMQP looks for a container with the `quarkus-dev-service-amqp` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-amqp` label set to the specified value. \nThis property is used when you need multiple shared AMQP brokers.","withinAMap":false,"defaultValue":"amqp","javaDocSiteLink":"","docMapKey":"service-name","configPhase":"BUILD_TIME","acceptedValues":null,"optional":false,"list":false,"passThroughMap":false,"withinAConfigGroup":true,"topLevelGrouping":"","enum":false}}]