Sync web site with Quarkus documentation

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

@@ -26524,7 +26524,7 @@ Kafka dev service container type.
 
 Redpanda, Strimzi and kafka-native container providers are supported. Default is redpanda.
 
-For Redpanda: See https://docs.redpanda.com/current/get-started/quick-start/ and https://hub.docker.com/r/vectorized/redpanda
+For Redpanda: See https://docs.redpanda.com/current/get-started/quick-start/ and https://hub.docker.com/r/redpandadata/redpanda
 
 For Strimzi: See https://github.com/strimzi/test-container and https://quay.io/repository/strimzi-test-container/test-container
 
@@ -61469,6 +61469,23 @@ endif::add-copy-button-to-env-var[]
 |list of string
 |
 
+a| [[quarkus-spring-cloud-config-client_quarkus-spring-cloud-config-ordinal]] [.property-path]##link:#quarkus-spring-cloud-config-client_quarkus-spring-cloud-config-ordinal[`quarkus.spring-cloud-config.ordinal`]##
+
+[.description]
+--
+Microprofile Config ordinal.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_SPRING_CLOUD_CONFIG_ORDINAL+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_SPRING_CLOUD_CONFIG_ORDINAL+++`
+endif::add-copy-button-to-env-var[]
+--
+|int
+|`450`
+
 
 h|[.extension-name]##Quartz##
 h|Type

_generated-doc/latest/config/quarkus-kafka-client.adoc

@@ -110,7 +110,7 @@ Kafka dev service container type.
 
 Redpanda, Strimzi and kafka-native container providers are supported. Default is redpanda.
 
-For Redpanda: See https://docs.redpanda.com/current/get-started/quick-start/ and https://hub.docker.com/r/vectorized/redpanda
+For Redpanda: See https://docs.redpanda.com/current/get-started/quick-start/ and https://hub.docker.com/r/redpandadata/redpanda
 
 For Strimzi: See https://github.com/strimzi/test-container and https://quay.io/repository/strimzi-test-container/test-container
 

_generated-doc/latest/config/quarkus-kafka-client_quarkus.kafka.adoc

@@ -110,7 +110,7 @@ Kafka dev service container type.
 
 Redpanda, Strimzi and kafka-native container providers are supported. Default is redpanda.
 
-For Redpanda: See https://docs.redpanda.com/current/get-started/quick-start/ and https://hub.docker.com/r/vectorized/redpanda
+For Redpanda: See https://docs.redpanda.com/current/get-started/quick-start/ and https://hub.docker.com/r/redpandadata/redpanda
 
 For Strimzi: See https://github.com/strimzi/test-container and https://quay.io/repository/strimzi-test-container/test-container
 

_generated-doc/latest/config/quarkus-kafka-client_quarkus.kafka.devservices.adoc

@@ -51,7 +51,7 @@ Kafka dev service container type.
 
 Redpanda, Strimzi and kafka-native container providers are supported. Default is redpanda.
 
-For Redpanda: See https://docs.redpanda.com/current/get-started/quick-start/ and https://hub.docker.com/r/vectorized/redpanda
+For Redpanda: See https://docs.redpanda.com/current/get-started/quick-start/ and https://hub.docker.com/r/redpandadata/redpanda
 
 For Strimzi: See https://github.com/strimzi/test-container and https://quay.io/repository/strimzi-test-container/test-container
 

_generated-doc/latest/config/quarkus-spring-cloud-config-client.adoc

@@ -300,6 +300,23 @@ endif::add-copy-button-to-env-var[]
 |list of string
 |
 
+a| [[quarkus-spring-cloud-config-client_quarkus-spring-cloud-config-ordinal]] [.property-path]##link:#quarkus-spring-cloud-config-client_quarkus-spring-cloud-config-ordinal[`quarkus.spring-cloud-config.ordinal`]##
+
+[.description]
+--
+Microprofile Config ordinal.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_SPRING_CLOUD_CONFIG_ORDINAL+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_SPRING_CLOUD_CONFIG_ORDINAL+++`
+endif::add-copy-button-to-env-var[]
+--
+|int
+|`450`
+
 |===
 
 ifndef::no-duration-note[]

_generated-doc/latest/config/quarkus-spring-cloud-config-client_quarkus.spring-cloud-config.adoc

@@ -300,6 +300,23 @@ endif::add-copy-button-to-env-var[]
 |list of string
 |
 
+a| [[quarkus-spring-cloud-config-client_quarkus-spring-cloud-config-ordinal]] [.property-path]##link:#quarkus-spring-cloud-config-client_quarkus-spring-cloud-config-ordinal[`quarkus.spring-cloud-config.ordinal`]##
+
+[.description]
+--
+Microprofile Config ordinal.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_SPRING_CLOUD_CONFIG_ORDINAL+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_SPRING_CLOUD_CONFIG_ORDINAL+++`
+endif::add-copy-button-to-env-var[]
+--
+|int
+|`450`
+
 |===
 
 ifndef::no-duration-note[]

_guides/_attributes.adoc

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

_guides/kafka-dev-services.adoc

@@ -56,8 +56,8 @@ Dev Services for Kafka supports https://redpanda.com[Redpanda], https://github/o
 and https://strimzi.io[Strimzi] (in https://github.com/apache/kafka/blob/trunk/config/kraft/README.md[Kraft] mode)  images.
 
 **Redpanda** is a Kafka compatible event streaming platform.
-Because it provides a fast startup times, Dev Services defaults to Redpanda images from `vectorized/redpanda`.
-You can select any version from https://hub.docker.com/r/vectorized/redpanda.
+Because it provides a fast startup times, Dev Services defaults to Redpanda images from `redpandadata/redpanda`.
+You can select any version from https://hub.docker.com/r/redpandadata/redpanda.
 
 **kafka-native** provides images of standard Apache Kafka distribution compiled to native binary using Quarkus and GraalVM.
 While still being _experimental_, it provides very fast startup times with small footprint.

_guides/native-reference.adoc

@@ -598,7 +598,7 @@ invoke Maven's `verify` goal with `-DskipITs=false -Dquarkus.test.integration-te
 generate the native image configuration.
 For example:
 
-[source,bash]
+[source,bash,subs=attributes+]
 ----
 $ ./mvnw verify -DskipITs=false -Dquarkus.test.integration-test-profile=test-with-native-agent
 ...
@@ -660,7 +660,7 @@ This can be useful to verify that the native integration tests work as expected,
 assuming that the JVM unit tests have generated the correct native image configuration.
 The typical workflow here would be to first run the integration tests with the native image agent as shown in the previous section:
 
-[source,bash]
+[source,bash,subs=attributes+]
 ----
 $ ./mvnw verify -DskipITs=false -Dquarkus.test.integration-test-profile=test-with-native-agent
 ...
@@ -671,7 +671,7 @@ $ ./mvnw verify -DskipITs=false -Dquarkus.test.integration-test-profile=test-wit
 And then request a native build passing in the configuration apply flag.
 A message during the native build process will indicate that the native image agent generated configuration files are being applied:
 
-[source,bash]
+[source,bash,subs=attributes+]
 ----
 $ ./mvnw verify -Dnative -Dquarkus.native.agent-configuration-apply
 ...
@@ -702,7 +702,7 @@ and confirm that the class and/or package making the call or being accessed is n
 If the missing entry is related to some resource,
 you should inspect the Quarkus build debug output and verify which resource patterns are being discarded, e.g.
 
-[source,bash]
+[source,bash,subs=attributes+]
 ----
 $ ./mvnw -X verify -DskipITs=false -Dquarkus.test.integration-test-profile=test-with-native-agent
 ...

_guides/observability-devservices-lgtm.adoc

@@ -30,7 +30,7 @@ Add the Quarkus Grafana OTel LGTM sink (where data goes) extension to your build
 [source,gradle,role="secondary asciidoc-tabs-target-sync-gradle"]
 .build.gradle
 ----
-implementation("quarkus-observability-devservices-lgtm")
+implementation("io.quarkus:quarkus-observability-devservices-lgtm")
 ----
 
 === Metrics

_guides/rest-client.adoc

@@ -325,6 +325,38 @@ public interface ExtensionsService {
 }
 ----
 
+=== Dynamic base URLs
+
+The REST client allows for a per invocation override of the base URL using the `io.quarkus.rest.client.reactive.Url` annotation.
+
+Here is a simple example:
+
+[source, java]
+----
+package org.acme.rest.client;
+
+import org.eclipse.microprofile.rest.client.inject.RegisterRestClient;
+
+import jakarta.ws.rs.GET;
+import jakarta.ws.rs.Path;
+import jakarta.ws.rs.PathParam;
+import jakarta.ws.rs.QueryParam;
+import java.util.Set;
+
+import io.quarkus.rest.client.reactive.Url;
+
+@Path("/extensions")
+@RegisterRestClient
+public interface ExtensionsService {
+
+    @GET
+    @Path("/stream/{stream}")
+    Set<Extension> getByStream(@Url String url, @PathParam("stream") String stream, @QueryParam("id") String id);
+}
+----
+
+When the `url` parameter is non-null, it will override the base URL that is configured for the client (the default base URL configuration is still mandatory).
+
 === Sending large payloads
 
 The REST Client is capable of sending arbitrarily large HTTP bodies without buffering the contents in memory, if one of the following types is used:

_guides/rest-virtual-threads.adoc

@@ -53,7 +53,7 @@ and in particular, adds the following dependencies:
 .build.gradle
 ----
 implementation("io.quarkus:quarkus-rest-jackson")
-implementation("quarkus-rest-client-jackson")
+implementation("io.quarkus:quarkus-rest-client-jackson")
 ----
 
 [NOTE]