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: "security, web"
+    categories: "web, security"
     id: security-authorize-web-endpoints-reference
     type: reference
     url: /guides/security-authorize-web-endpoints-reference
@@ -18,7 +18,7 @@ types:
   - title: Command Mode Applications
     filename: command-mode-reference.adoc
     summary: This reference guide explains how to develop command line applications with Quarkus.
-    categories: "command-line, core"
+    categories: "core, command-line"
     type: reference
     url: /guides/command-mode-reference
   - title: Configuration Reference Guide
@@ -55,7 +55,7 @@ types:
   - title: Logging configuration
     filename: logging.adoc
     summary: "Read about the use of logging API in Quarkus, configuring logging output, and using logging adapters to unify the output from other logging APIs."
-    categories: "getting-started, core, observability"
+    categories: "getting-started, observability, core"
     id: logging
     type: reference
     url: /guides/logging
@@ -159,28 +159,28 @@ types:
   - title: Authentication mechanisms in Quarkus
     filename: security-authentication-mechanisms.adoc
     summary: "The Quarkus Security framework supports multiple authentication mechanisms, which you can use to secure your applications."
-    categories: "security, web"
+    categories: "web, security"
     id: security-authentication-mechanisms
     type: concepts
     url: /guides/security-authentication-mechanisms
   - title: Basic authentication
     filename: security-basic-authentication.adoc
     summary: HTTP Basic authentication is one of the least resource-demanding techniques that enforce access controls to web resources.
-    categories: "security, web"
+    categories: "web, security"
     id: security-basic-authentication
     type: concepts
     url: /guides/security-basic-authentication
   - title: Configuring Well-Known OpenID Connect Providers
     filename: security-openid-connect-providers.adoc
     summary: This document explains how to configure well-known social OIDC and OAuth2 providers.
-    categories: "security, web"
+    categories: "web, security"
     id: security-openid-connect-providers
     type: concepts
     url: /guides/security-openid-connect-providers
   - title: "Duplicated context, context locals, asynchronous processing and propagation"
     filename: duplicated-context.adoc
     summary: "When using a traditional, blocking, and synchronous framework, processing of each request is performed in a dedicated thread."
-    categories: "core, architecture"
+    categories: "architecture, core"
     id: duplicated-context
     type: concepts
     url: /guides/duplicated-context
@@ -194,21 +194,21 @@ types:
   - title: OpenID Connect (OIDC) Bearer token authentication
     filename: security-oidc-bearer-token-authentication.adoc
     summary: Secure HTTP access to Jakarta REST (formerly known as JAX-RS) endpoints in your application with Bearer token authentication by using the Quarkus OpenID Connect (OIDC) extension.
-    categories: "security, web"
+    categories: "web, security"
     id: security-oidc-bearer-token-authentication
     type: concepts
     url: /guides/security-oidc-bearer-token-authentication
   - title: OpenID Connect authorization code flow mechanism for protecting web applications
     filename: security-oidc-code-flow-authentication.adoc
     summary: "To protect your web applications, you can use the industry-standard OpenID Connect (OIDC) Authorization Code Flow mechanism provided by the Quarkus OIDC extension."
-    categories: "security, web"
+    categories: "web, security"
     id: security-oidc-code-flow-authentication
     type: concepts
     url: /guides/security-oidc-code-flow-authentication
   - title: Proactive authentication
     filename: security-proactive-authentication.adoc
     summary: Proactive authentication is enabled in Quarkus by default.
-    categories: "security, web"
+    categories: "web, security"
     id: security-proactive-authentication
     type: concepts
     url: /guides/security-proactive-authentication
@@ -236,7 +236,7 @@ types:
   - title: Security vulnerability detection and reporting in Quarkus
     filename: security-vulnerability-detection.adoc
     summary: Most of the Quarkus tags are registered in the US National Vulnerability Database (NVD) in Common Platform Enumeration (CPE) name format.
-    categories: "security, contributing"
+    categories: "contributing, security"
     id: security-vulnerability-detection
     type: concepts
     url: /guides/security-vulnerability-detection
@@ -265,7 +265,7 @@ types:
   - title: Use virtual threads in REST applications
     filename: resteasy-reactive-virtual-threads.adoc
     summary: How to use virtual threads in a REST application
-    categories: "core, web"
+    categories: "web, core"
     id: resteasy-reactive-virtual-threads
     type: howto
     url: /guides/resteasy-reactive-virtual-threads
@@ -312,7 +312,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: "security, web"
+    categories: "web, security"
     id: security-oidc-code-flow-authentication-tutorial
     type: tutorial
     url: /guides/security-oidc-code-flow-authentication-tutorial
@@ -394,7 +394,7 @@ types:
   - title: AppCDS
     filename: appcds.adoc
     summary: This reference guide explains how to enable AppCDS with Quarkus.
-    categories: "core, cloud"
+    categories: "cloud, core"
     type: guide
     url: /guides/appcds
   - title: Application Data Caching
@@ -957,14 +957,14 @@ types:
   - title: Quarkus and Gradle
     filename: gradle-tooling.adoc
     summary: Develop and build your Quarkus application with Gradle
-    categories: "tooling, native"
+    categories: "native, tooling"
     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: "tooling, native"
+    categories: "native, tooling"
     id: maven-tooling
     type: guide
     url: /guides/maven-tooling
@@ -1062,7 +1062,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: "observability, web"
+    categories: "web, observability"
     type: guide
     url: /guides/smallrye-fault-tolerance
   - title: SmallRye GraphQL
@@ -1092,14 +1092,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: "native, core, tooling"
     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: "core, native, writing-extensions"
+    categories: "writing-extensions, native, core"
     type: guide
     url: /guides/writing-native-applications-tips
   - title: Using Apache Kafka Streams
@@ -1228,7 +1228,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: "native, core, security"
     type: guide
     url: /guides/native-and-ssl
   - title: Using Security with .properties File
@@ -1341,13 +1341,13 @@ 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: "data, web"
+    categories: "web, data"
     type: guide
     url: /guides/validation
   - title: Writing JSON REST Services
     filename: rest-json.adoc
     summary: JSON is now the lingua franca between microservices.
-    categories: "serialization, web"
+    categories: "web, serialization"
     type: guide
     url: /guides/rest-json
   - title: Writing REST Services with RESTEasy Reactive

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

@@ -75,40 +75,40 @@ endif::add-copy-button-to-env-var[]
 |`Build system locale`
 
 
-a| [[quarkus-core_quarkus.init-and-exit]]`link:#quarkus-core_quarkus.init-and-exit[quarkus.init-and-exit]`
+a| [[quarkus-core_quarkus.args]]`link:#quarkus-core_quarkus.args[quarkus.args]`
 
 
 [.description]
 --
-true to quit exit right after the initialization. The option is not meant be used directly by users.
+The arguments passed to the command line.
+
+We don't make it a list as the args are separated by a space, not a comma.
 
 ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_INIT_AND_EXIT+++[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_ARGS+++[]
 endif::add-copy-button-to-env-var[]
 ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_INIT_AND_EXIT+++`
+Environment variable: `+++QUARKUS_ARGS+++`
 endif::add-copy-button-to-env-var[]
---|boolean 
-|`false`
+--|string 
+|
 
 
-a| [[quarkus-core_quarkus.args]]`link:#quarkus-core_quarkus.args[quarkus.args]`
+a| [[quarkus-core_quarkus.init-and-exit]]`link:#quarkus-core_quarkus.init-and-exit[quarkus.init-and-exit]`
 
 
 [.description]
 --
-The arguments passed to the command line.
-
-We don't make it a list as the args are separated by a space, not a comma.
+true to quit exit right after the initialization. The option is not meant be used directly by users.
 
 ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_ARGS+++[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_INIT_AND_EXIT+++[]
 endif::add-copy-button-to-env-var[]
 ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_ARGS+++`
+Environment variable: `+++QUARKUS_INIT_AND_EXIT+++`
 endif::add-copy-button-to-env-var[]
---|string 
-|
+--|boolean 
+|`false`
 
 
 a| [[quarkus-core_quarkus.profile]]`link:#quarkus-core_quarkus.profile[quarkus.profile]`

_generated-doc/main/config/quarkus-datasource-config-group-data-source-build-time-config.adoc

@@ -324,4 +324,84 @@ endif::add-copy-button-to-env-var[]
 --|boolean 
 |`false`
 
+
+a| [[quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.username]]`link:#quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.username[quarkus.datasource.username]`
+
+`link:#quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.username[quarkus.datasource."datasource-name".username]`
+
+
+[.description]
+--
+The datasource username
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_DATASOURCE_USERNAME+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_DATASOURCE_USERNAME+++`
+endif::add-copy-button-to-env-var[]
+--|string 
+|
+
+
+a| [[quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.password]]`link:#quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.password[quarkus.datasource.password]`
+
+`link:#quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.password[quarkus.datasource."datasource-name".password]`
+
+
+[.description]
+--
+The datasource password
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_DATASOURCE_PASSWORD+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_DATASOURCE_PASSWORD+++`
+endif::add-copy-button-to-env-var[]
+--|string 
+|
+
+
+a| [[quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.credentials-provider]]`link:#quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.credentials-provider[quarkus.datasource.credentials-provider]`
+
+`link:#quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.credentials-provider[quarkus.datasource."datasource-name".credentials-provider]`
+
+
+[.description]
+--
+The credentials provider name
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_DATASOURCE_CREDENTIALS_PROVIDER+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_DATASOURCE_CREDENTIALS_PROVIDER+++`
+endif::add-copy-button-to-env-var[]
+--|string 
+|
+
+
+a| [[quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.credentials-provider-name]]`link:#quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.credentials-provider-name[quarkus.datasource.credentials-provider-name]`
+
+`link:#quarkus-datasource-config-group-data-source-build-time-config_quarkus.datasource.credentials-provider-name[quarkus.datasource."datasource-name".credentials-provider-name]`
+
+
+[.description]
+--
+The credentials provider bean name.
+
+This is a bean name (as in `@Named`) of a bean that implements `CredentialsProvider`. It is used to select the credentials provider bean when multiple exist. This is unnecessary when there is only one credentials provider available.
+
+For Vault, the credentials provider bean name is `vault-credentials-provider`.
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_DATASOURCE_CREDENTIALS_PROVIDER_NAME+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_DATASOURCE_CREDENTIALS_PROVIDER_NAME+++`
+endif::add-copy-button-to-env-var[]
+--|string 
+|
+
 |===