This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 8e904a3bb0f7 CAMEL-27049: upgrade guide notes for the camel-main
secret options masked in 4.22.3 and 4.18.6 (#30242)
8e904a3bb0f7 is described below
commit 8e904a3bb0f765f92c14ce0c87f596fe9de254c4
Author: Claus Ibsen <[email protected]>
AuthorDate: Mon Nov 16 23:10:15 2026 +0100
CAMEL-27049: upgrade guide notes for the camel-main secret options masked
in 4.22.3 and 4.18.6 (#30242)
The 4.22.3 and 4.18.6 notes for the camel-main options flagged secret that
are now sensitive keys (backports #30240 and #30241). The 4.18.6 note has no
secret policy paragraph, and says that the IBM vault options
eventStreamUsername and eventStreamPassword are now flagged secret.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: Claus Ibsen <[email protected]>
---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 10 ++++++++++
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 15 +++++++++++++++
2 files changed, 25 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index 91b17ada2a78..8704f01cae28 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -975,6 +975,16 @@ catalog version for Camel core dependencies in the
generated project. For exampl
uses Camel 4.8.0 instead of the running CLI's version when that catalog is
available. Set `--camel-version` explicitly
to retain a different core dependency version.
+=== camel-main - the server and vault options flagged secret are sensitive keys
+
+The options `camel.server.jwtKeystorePassword`,
`camel.management.jwtKeystorePassword`,
+`camel.vault.azure.eventhubConnectionString`, `camel.vault.azure.tenantId` and
`camel.vault.gcp.serviceAccountKey` are
+flagged secret, and are now also sensitive keys, like the other secret
options. The options
+`camel.vault.ibm.eventStreamUsername` and
`camel.vault.ibm.eventStreamPassword` are now flagged secret as well.
+The Camel Main auto-configuration summary shows the value of these options as
`xxxxxx`.
+These options are matched by their whole key. Component and endpoint options
with the same name, such as `tenantId` or
+`serviceAccountKey`, are not affected.
+
== Upgrading from 4.18.4 to 4.18.5
=== camel-azure-eventhubs
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
index 17405c7e612b..59dd5fd7c2c7 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
@@ -906,6 +906,21 @@ catalog version for Camel core dependencies in the
generated project. For exampl
uses Camel 4.8.0 instead of the running CLI's version when that catalog is
available. Set `--camel-version` explicitly
to retain a different core dependency version.
+=== camel-main - the server and vault options flagged secret are sensitive keys
+
+The options `camel.server.jwtKeystorePassword`,
`camel.management.jwtKeystorePassword`,
+`camel.vault.azure.eventhubConnectionString`, `camel.vault.azure.tenantId`,
`camel.vault.gcp.serviceAccountKey`,
+`camel.vault.ibm.eventStreamUsername` and
`camel.vault.ibm.eventStreamPassword` are flagged secret, and are now also
+sensitive keys, like the other secret options. The Camel Main
auto-configuration summary shows their value as `xxxxxx`.
+These options are matched by their whole key. Component and endpoint options
with the same name, such as `tenantId` or
+`serviceAccountKey`, are not affected.
+
+The `camel.security.secretPolicy` check now also reports these options when
they are configured as plain text,
+including a value set through an environment variable. By default this logs a
warning, and with
+`camel.main.profile=prod` the startup fails. Configure them with a property
placeholder or a vault reference instead.
+A file location in `camel.vault.gcp.serviceAccountKey`, such as
`file:/etc/gcp/sa.json`, is also reported. It can go
+behind a property placeholder too.
+
== Upgrading from 4.22.1 to 4.22.2
=== camel-lra - only an LRA hosted by the configured coordinator is joined