Sync documentation of main branch

Author: actions-user

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

@@ -62705,6 +62705,27 @@ endif::add-copy-button-to-env-var[]
 |string
 |
 
+a|icon:lock[title=Fixed at build time] [[quarkus-quartz_quarkus-quartz-driver-delegate]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-driver-delegate[`quarkus.quartz.driver-delegate`]##
+
+[.description]
+--
+Allows users to specify fully qualified class name for a custom JDBC driver delegate.
+
+This property is optional and leaving it empty will result in Quarkus automatically choosing appropriate default driver delegate implementation.
+
+Note that any custom implementation has to be a subclass of existing Quarkus implementation such as `io.quarkus.quartz.runtime.jdbc.QuarkusPostgreSQLDelegate` or `io.quarkus.quartz.runtime.jdbc.QuarkusMSSQLDelegate`
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_QUARTZ_DRIVER_DELEGATE+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_QUARTZ_DRIVER_DELEGATE+++`
+endif::add-copy-button-to-env-var[]
+--
+|string
+|
+
 a|icon:lock[title=Fixed at build time] [[quarkus-quartz_quarkus-quartz-serialize-job-data]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-serialize-job-data[`quarkus.quartz.serialize-job-data`]##
 
 [.description]
@@ -62898,6 +62919,27 @@ endif::add-copy-button-to-env-var[]
 a|`smart-policy`, `ignore-misfire-policy`, `fire-now`, `simple-trigger-reschedule-now-with-existing-repeat-count`, `simple-trigger-reschedule-now-with-remaining-repeat-count`, `simple-trigger-reschedule-next-with-remaining-count`, `simple-trigger-reschedule-next-with-existing-count`, `cron-trigger-do-nothing`
 |`smart-policy`
 
+a| [[quarkus-quartz_quarkus-quartz-unsupported-properties-full-property-key]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-unsupported-properties-full-property-key[`quarkus.quartz.unsupported-properties."full-property-key"`]##
+
+[.description]
+--
+Properties that should be passed on directly to Quartz. Use the full configuration property key here, for instance ``quarkus.quartz.unsupported-properties."org.quartz.scheduler.jmx.export" = true`)`.
+
+Properties set here are completely unsupported: as Quarkus doesn't generally know about these properties and their purpose, there is absolutely no guarantee that they will work correctly, and even if they do, that may change when upgrading to a newer version of Quarkus (even just a micro/patch version).
+
+Consider using a supported configuration property before falling back to unsupported ones. If none exists, make sure to file a feature request so that a supported configuration property can be added to Quarkus, and more importantly so that the configuration property is tested regularly.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_QUARTZ_UNSUPPORTED_PROPERTIES__FULL_PROPERTY_KEY_+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_QUARTZ_UNSUPPORTED_PROPERTIES__FULL_PROPERTY_KEY_+++`
+endif::add-copy-button-to-env-var[]
+--
+|Map<String,String>
+|
+
 a| [[quarkus-quartz_quarkus-quartz-run-blocking-scheduled-method-on-quartz-thread]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-run-blocking-scheduled-method-on-quartz-thread[`quarkus.quartz.run-blocking-scheduled-method-on-quartz-thread`]##
 
 [.description]

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

@@ -129,6 +129,27 @@ endif::add-copy-button-to-env-var[]
 |string
 |
 
+a|icon:lock[title=Fixed at build time] [[quarkus-quartz_quarkus-quartz-driver-delegate]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-driver-delegate[`quarkus.quartz.driver-delegate`]##
+
+[.description]
+--
+Allows users to specify fully qualified class name for a custom JDBC driver delegate.
+
+This property is optional and leaving it empty will result in Quarkus automatically choosing appropriate default driver delegate implementation.
+
+Note that any custom implementation has to be a subclass of existing Quarkus implementation such as `io.quarkus.quartz.runtime.jdbc.QuarkusPostgreSQLDelegate` or `io.quarkus.quartz.runtime.jdbc.QuarkusMSSQLDelegate`
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_QUARTZ_DRIVER_DELEGATE+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_QUARTZ_DRIVER_DELEGATE+++`
+endif::add-copy-button-to-env-var[]
+--
+|string
+|
+
 a|icon:lock[title=Fixed at build time] [[quarkus-quartz_quarkus-quartz-serialize-job-data]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-serialize-job-data[`quarkus.quartz.serialize-job-data`]##
 
 [.description]
@@ -322,6 +343,27 @@ endif::add-copy-button-to-env-var[]
 a|`smart-policy`, `ignore-misfire-policy`, `fire-now`, `simple-trigger-reschedule-now-with-existing-repeat-count`, `simple-trigger-reschedule-now-with-remaining-repeat-count`, `simple-trigger-reschedule-next-with-remaining-count`, `simple-trigger-reschedule-next-with-existing-count`, `cron-trigger-do-nothing`
 |`smart-policy`
 
+a| [[quarkus-quartz_quarkus-quartz-unsupported-properties-full-property-key]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-unsupported-properties-full-property-key[`quarkus.quartz.unsupported-properties."full-property-key"`]##
+
+[.description]
+--
+Properties that should be passed on directly to Quartz. Use the full configuration property key here, for instance ``quarkus.quartz.unsupported-properties."org.quartz.scheduler.jmx.export" = true`)`.
+
+Properties set here are completely unsupported: as Quarkus doesn't generally know about these properties and their purpose, there is absolutely no guarantee that they will work correctly, and even if they do, that may change when upgrading to a newer version of Quarkus (even just a micro/patch version).
+
+Consider using a supported configuration property before falling back to unsupported ones. If none exists, make sure to file a feature request so that a supported configuration property can be added to Quarkus, and more importantly so that the configuration property is tested regularly.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_QUARTZ_UNSUPPORTED_PROPERTIES__FULL_PROPERTY_KEY_+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_QUARTZ_UNSUPPORTED_PROPERTIES__FULL_PROPERTY_KEY_+++`
+endif::add-copy-button-to-env-var[]
+--
+|Map<String,String>
+|
+
 a| [[quarkus-quartz_quarkus-quartz-run-blocking-scheduled-method-on-quartz-thread]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-run-blocking-scheduled-method-on-quartz-thread[`quarkus.quartz.run-blocking-scheduled-method-on-quartz-thread`]##
 
 [.description]

_generated-doc/main/config/quarkus-quartz_quarkus.quartz.adoc

@@ -129,6 +129,27 @@ endif::add-copy-button-to-env-var[]
 |string
 |
 
+a|icon:lock[title=Fixed at build time] [[quarkus-quartz_quarkus-quartz-driver-delegate]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-driver-delegate[`quarkus.quartz.driver-delegate`]##
+
+[.description]
+--
+Allows users to specify fully qualified class name for a custom JDBC driver delegate.
+
+This property is optional and leaving it empty will result in Quarkus automatically choosing appropriate default driver delegate implementation.
+
+Note that any custom implementation has to be a subclass of existing Quarkus implementation such as `io.quarkus.quartz.runtime.jdbc.QuarkusPostgreSQLDelegate` or `io.quarkus.quartz.runtime.jdbc.QuarkusMSSQLDelegate`
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_QUARTZ_DRIVER_DELEGATE+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_QUARTZ_DRIVER_DELEGATE+++`
+endif::add-copy-button-to-env-var[]
+--
+|string
+|
+
 a|icon:lock[title=Fixed at build time] [[quarkus-quartz_quarkus-quartz-serialize-job-data]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-serialize-job-data[`quarkus.quartz.serialize-job-data`]##
 
 [.description]
@@ -322,6 +343,27 @@ endif::add-copy-button-to-env-var[]
 a|`smart-policy`, `ignore-misfire-policy`, `fire-now`, `simple-trigger-reschedule-now-with-existing-repeat-count`, `simple-trigger-reschedule-now-with-remaining-repeat-count`, `simple-trigger-reschedule-next-with-remaining-count`, `simple-trigger-reschedule-next-with-existing-count`, `cron-trigger-do-nothing`
 |`smart-policy`
 
+a| [[quarkus-quartz_quarkus-quartz-unsupported-properties-full-property-key]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-unsupported-properties-full-property-key[`quarkus.quartz.unsupported-properties."full-property-key"`]##
+
+[.description]
+--
+Properties that should be passed on directly to Quartz. Use the full configuration property key here, for instance ``quarkus.quartz.unsupported-properties."org.quartz.scheduler.jmx.export" = true`)`.
+
+Properties set here are completely unsupported: as Quarkus doesn't generally know about these properties and their purpose, there is absolutely no guarantee that they will work correctly, and even if they do, that may change when upgrading to a newer version of Quarkus (even just a micro/patch version).
+
+Consider using a supported configuration property before falling back to unsupported ones. If none exists, make sure to file a feature request so that a supported configuration property can be added to Quarkus, and more importantly so that the configuration property is tested regularly.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_QUARTZ_UNSUPPORTED_PROPERTIES__FULL_PROPERTY_KEY_+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_QUARTZ_UNSUPPORTED_PROPERTIES__FULL_PROPERTY_KEY_+++`
+endif::add-copy-button-to-env-var[]
+--
+|Map<String,String>
+|
+
 a| [[quarkus-quartz_quarkus-quartz-run-blocking-scheduled-method-on-quartz-thread]] [.property-path]##link:#quarkus-quartz_quarkus-quartz-run-blocking-scheduled-method-on-quartz-thread[`quarkus.quartz.run-blocking-scheduled-method-on-quartz-thread`]##
 
 [.description]

_versions/main/guides/_attributes.adoc

@@ -19,7 +19,7 @@
 :logstash-image: docker.io/elastic/logstash:8.15.0
 :kibana-image: docker.io/elastic/kibana:8.15.0
 :keycloak-docker-image: quay.io/keycloak/keycloak:25.0.6
-:jandex-version: 3.2.2
+:jandex-version: 3.2.3
 :jandex-gradle-plugin-version: 1.0.0
 :kotlin-version: 2.0.21
 :grpc-version: 1.65.1

_versions/main/guides/aws-lambda-http.adoc

@@ -88,6 +88,18 @@ NOTE: If you are building on a non-Linux system, you will need to also pass in a
 Lambda requires Linux binaries.  You can do this by passing `-Dquarkus.native.container-build=true` to your build command.
 This requires you to have Docker installed locally, however.
 
+[NOTE]
+====
+According to the https://docs.aws.amazon.com/linux/al2023/ug/system-requirements.html#system-requirements-cpu-x86-64[AWS documentation], AL2023
+x86-64 binaries are built for the x86-64-**v2** revision of the x86-64 architecture.
+In Quarkus, the default value of xref:building-native-image.adoc#quarkus-core_quarkus-native-march[quarkus.native.march] is x86-64-**v3**.
+This could cause
+https://repost.aws/questions/QUBVnl6hn-Toe1LPr1qjOXzg/lambda-failed-with-java-compiled-into-machine-code[issues] if AWS Lambda provisions older
+hardware.
+To maximize Lambda compatibility, you can set `quarkus.native.march` to `x86-64-v2`.
+See the xref:native-reference.adoc#work-around-missing-cpu-features[Native Reference] guide for more information.
+====
+
 include::{includes}/devtools/build-native-container.adoc[]
 
 == Extra Build Generated Files

_versions/main/guides/opentelemetry-logging.adoc

@@ -5,6 +5,7 @@ https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 ////
 = Using OpenTelemetry Logging
 include::_attributes.adoc[]
+:extension-status: preview
 :categories: observability
 :summary: This guide explains how your Quarkus application can utilize OpenTelemetry Logging to provide distributed logging for interactive web applications.
 :topics: observability,opentelemetry,logging
@@ -13,9 +14,11 @@ include::_attributes.adoc[]
 This guide explains how your Quarkus application can utilize https://opentelemetry.io/[OpenTelemetry] (OTel) to provide
 distributed logging for interactive web applications.
 
+include::{includes}/extension-status.adoc[]
+
 [NOTE]
 ====
-- OpenTelemetry Logging is disabled by default.
+- OpenTelemetry Logging is considered _tech preview_ and is disabled by default.
 - The xref:opentelemetry.adoc[OpenTelemetry Guide] is available with signal independent information about the OpenTelemetry extension.
 ====
 

_versions/main/guides/opentelemetry-metrics.adoc

@@ -5,6 +5,7 @@ https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 ////
 = Using OpenTelemetry Metrics
 include::_attributes.adoc[]
+:extension-status: preview
 :categories: observability
 :summary: This guide explains how your Quarkus application can utilize OpenTelemetry to provide metrics for interactive web applications.
 :topics: observability,opentelemetry,metrics
@@ -13,9 +14,11 @@ include::_attributes.adoc[]
 This guide explains how your Quarkus application can utilize https://opentelemetry.io/[OpenTelemetry] (OTel) to provide
 metrics for interactive web applications.
 
+include::{includes}/extension-status.adoc[]
+
 [NOTE]
 ====
-- OpenTelemetry Metrics is disabled by default and Quarkus does not produce automatic metrics for it.
+- OpenTelemetry Metrics is considered _tech preview_ and is disabled by default.
 - The xref:opentelemetry.adoc[OpenTelemetry Guide] is available with signal independent information about the OpenTelemetry extension.
 - If you search more information about OpenTelemetry Tracing, please refer to the xref:opentelemetry-tracing.adoc[OpenTelemetry Tracing Guide].
 ====

_versions/main/guides/opentelemetry.adoc

@@ -18,15 +18,14 @@ On these page we show the signal independent features of the extension.
 
 [NOTE]
 ====
-- The old OpenTelemetry guide has been split into this generic guide, the xref:opentelemetry-tracing.adoc[OpenTelemetry Tracing Guide] and the new  xref:opentelemetry-metrics.adoc[OpenTelemetry Metrics Guide] has been created.
-- OpenTelemetry Logging is not yet supported.
+- The old OpenTelemetry guide has been split into this generic guide, the xref:opentelemetry-tracing.adoc[OpenTelemetry Tracing Guide], the new xref:opentelemetry-metrics.adoc[OpenTelemetry Metrics Guide] and the xref:opentelemetry-logging.adoc[OpenTelemetry Logging Guide].
 - The use of *the https://opentelemetry.io/docs/instrumentation/java/automatic/[OpenTelemetry Agent] is not needed nor recommended*. Quarkus Extensions and the libraries they provide, are directly instrumented. That agent doesn't work with native mode.
 ====
 
 == Introduction
 https://opentelemetry.io/docs/what-is-opentelemetry/[OpenTelemetry] is an Observability framework and toolkit designed to create and manage telemetry data such as traces, metrics, and logs. Crucially, OpenTelemetry is vendor- and tool-agnostic.
 
-Quarkus provides manual and automatic instrumentation for tracing and manual instrumentation  capabilities for metrics.
+Quarkus provides manual and automatic instrumentation for tracing and manual instrumentation capabilities for metrics.
 
 This will allow Quarkus based applications to be observable by tools and services supporting OpenTelemetry.