Sync documentation of main branch

Author: actions-user

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

@@ -12120,7 +12120,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-More hosts allowed for Dev UI Comma separated list of valid URLs, e.g.: www.quarkus.io, myhost.com (This can also be a regex) By default localhost and 127.0.0.1 will always be allowed
+More hosts allowed for Dev UI Comma separated list of valid URLs, e.g.: www.quarkus.io, myhost.com (This can also be a regex, e.g.: ^(++[++A-Za-z0-9-++]++{plus}).apps.myhost.com) By default localhost and 127.0.0.1 will always be allowed Note: Wildcards are not supported (e.g.: ++*++.apps.myhost.com)
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -61373,7 +61373,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_CONSOLE_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 
@@ -61632,7 +61632,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_FILE_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 
@@ -61891,7 +61891,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_SYSLOG_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 
@@ -62150,7 +62150,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_SOCKET_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 

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

@@ -78,7 +78,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-More hosts allowed for Dev UI Comma separated list of valid URLs, e.g.: www.quarkus.io, myhost.com (This can also be a regex) By default localhost and 127.0.0.1 will always be allowed
+More hosts allowed for Dev UI Comma separated list of valid URLs, e.g.: www.quarkus.io, myhost.com (This can also be a regex, e.g.: ^(++[++A-Za-z0-9-++]++{plus}).apps.myhost.com) By default localhost and 127.0.0.1 will always be allowed Note: Wildcards are not supported (e.g.: ++*++.apps.myhost.com)
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-devui_quarkus.dev-ui.adoc

@@ -78,7 +78,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-More hosts allowed for Dev UI Comma separated list of valid URLs, e.g.: www.quarkus.io, myhost.com (This can also be a regex) By default localhost and 127.0.0.1 will always be allowed
+More hosts allowed for Dev UI Comma separated list of valid URLs, e.g.: www.quarkus.io, myhost.com (This can also be a regex, e.g.: ^(++[++A-Za-z0-9-++]++{plus}).apps.myhost.com) By default localhost and 127.0.0.1 will always be allowed Note: Wildcards are not supported (e.g.: ++*++.apps.myhost.com)
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-logging-json.adoc

@@ -262,7 +262,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_CONSOLE_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 
@@ -521,7 +521,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_FILE_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 
@@ -780,7 +780,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_SYSLOG_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 
@@ -1039,7 +1039,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_SOCKET_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 

_generated-doc/main/config/quarkus-logging-json_quarkus.log.adoc

@@ -262,7 +262,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_CONSOLE_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 
@@ -521,7 +521,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_FILE_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 
@@ -780,7 +780,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_SYSLOG_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 
@@ -1039,7 +1039,7 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_LOG_SOCKET_JSON_LOG_FORMAT+++`
 endif::add-copy-button-to-env-var[]
 --
-a|`default`, `ecs`
+a|`default`, `ecs`, `gcp`
 |`+++default+++`
 
 

_versions/main/guides/logging.adoc

@@ -363,6 +363,8 @@ Although the root logger's handlers are usually configured directly via `quarkus
 
 == Logging format
 
+=== Human-readable text
+
 {project-name} uses a pattern-based logging formatter that generates human-readable text logs by default, but you can also configure the format for each log handler by using a dedicated property.
 
 For the console handler, the property is `quarkus.log.console.format`.
@@ -399,14 +401,8 @@ The logging format string supports the following symbols:
 |%x|Nested Diagnostics context values|Renders all the values from Nested Diagnostics Context in format `{value1.value2}`.
 |===
 
-
-[id="alt-console-format"]
-=== Alternative console logging formats
-
-Changing the console log format is useful, for example, when the console output of the Quarkus application is captured by a service that processes and stores the log information for later analysis.
-
 [id="json-logging"]
-==== JSON logging format
+=== JSON logging format
 
 The `quarkus-logging-json` extension might be employed to add support for the JSON logging format and its related configuration.
 
@@ -441,7 +437,21 @@ This can be achieved using different profiles, as shown in the following configu
 %test.quarkus.log.console.json.enabled=false
 ----
 
-===== Configuration
++
+. Choose the JSON logging format by setting the config property:
+[source, properties]
+----
+quarkus.log.console.json.log-format
+----
+This case will set the format for the console. The config values are:
+
+* *default*: Will generate structured logging based on the `key,values` present in the log record. MDC and NDC data will be also included nested in `mdc` and `ndc` fields.
+* *ecs*: https://www.elastic.co/docs/reference/ecs/ecs-field-reference[Elastic Common Fields]. Some default fields names are modified and some otheres are added to better comply with ECS. Namely: `@timestamp`,`log.logger`, `log.level`, `process.pid`, `process.name`, `process.thread.name`, `process.thread.id`, `host.hostname`, `event.sequence`, `error.message`, `error.stack_trace`, `ecs.version`, `data_stream.type`, `service.name`, `service.version` and `service.environment`.
+* *gcp*: https://cloud.google.com/logging/docs/structured-logging#structured_logging_special_fields[Google Cloud]. Follows the `Default` format and when the xref:opentelemetry-tracing.adoc[OpenTelemetry] is used, tracing data present in the `mdc` field is flattened and copied to `spanId`,  `traceSampled` and `trace`, but this last one with a prefix. GCP requires the `trace` to follow this semantic: `"projects/<my-trace-project>/traces/12345"`. Where `<my-trace-project>` has the same value as the `quarkus.application.name` config property.
++
+
+
+==== Configuration
 
 Configure the JSON logging extension using supported properties to customize its behavior.
 

_versions/main/guides/podman.adoc

@@ -46,8 +46,8 @@ On systems which involve a Podman Machine managed VM (Mac & Windows), container
 
 [source,bash]
 ----
-podman machine set --rootful=true # or false
 podman machine stop
+podman machine set --rootful=true # or false
 podman machine start
 ----
 

_versions/main/guides/websockets-next-reference.adoc

@@ -1291,21 +1291,25 @@ public class MyBean {
         WebSocketClientConnection connection = connector
             .baseUri(uri) <2>
             .pathParam("name", "Roxanne") <3>
+            .customizeOptions((connectOptions, clientOptions) -> {  <4>
+               // ...
+            })
             .connectAndAwait();
-        connection.sendTextAndAwait("Hi!"); <4>
+        connection.sendTextAndAwait("Hi!"); <5>
     }
 }
 ----
 <1> Inject the connector for `ClientEndpoint`.
 <2> If the base `URI` is not supplied we attempt to obtain the value from the config. The key consists of the client id and the `.base-uri` suffix.
 <3> Set the path param value. Throws `IllegalArgumentException` if the client endpoint path does not contain a parameter with the given name.
-<4> Use the connection to send messages, if needed.
+<4> Optionally, customize client and connection options not configurable with the connector API or Quarkus configuration.
+<5> Use the connection to send messages, if needed.
 
 NOTE: If an application attempts to inject a connector for a missing endpoint, an error is thrown.
 
 Connectors are not thread-safe and should not be used concurrently.
 Connectors should also not be reused. 
-If you need to create multiple connections in a row you'll need to obtain a new connetor instance programmatically using `Instance#get()`:
+If you need to create multiple connections in a row you'll need to obtain a new connector instance programmatically using `Instance#get()`:
 
 [source, java]
 ----
@@ -1350,6 +1354,9 @@ public class MyBean {
             .onTextMessage((c, m) -> { <5>
                // ...
             })
+            .customizeOptions((connectOptions, clientOptions) -> {  <6>
+               // ...
+            })
             .connectAndAwait();
     }
 }
@@ -1359,6 +1366,7 @@ public class MyBean {
 <3> The additional path that should be appended to the base URI.
 <4> Set the execution model for callback handlers. By default, the callback may block the current thread. However in this case, the callback is executed on the event loop and may not block the current thread.
 <5> The lambda will be called for every text message sent from the server.
+<6> Optionally, customize client and connection options not configurable with the connector API or Quarkus configuration.
 
 The basic connector is closer to a low-level API and is reserved for advanced users.
 However, unlike others low-level WebSocket clients, it is still a CDI bean and can be injected in other beans.