Claus Ibsen created CAMEL-25101:
-----------------------------------
Summary: camel-main - The "Property not auto-configured" warnings
are never logged
Key: CAMEL-25101
URL: https://issues.apache.org/jira/browse/CAMEL-25101
Project: Camel
Issue Type: Bug
Components: camel-main
Reporter: Claus Ibsen
camel-main logs a WARN "Property not auto-configured: ..." for properties that
could not be applied (such as a typo in a key) when
{{camel.main.autoConfigurationFailFast=false}}. These warnings are never logged.
The property groups are {{OrderedLocationProperties}}, and
{{BaseOrderedProperties}} (camel-util) stores its data in a private map but
does not override {{forEach}} (and {{getOrDefault}}, {{putIfAbsent}},
{{compute}}, {{merge}}, {{replace}}, {{equals}}/{{hashCode}}, {{clone}}), so
{{forEach}} iterates the empty inherited {{Hashtable}} and nothing is logged.
When fixing {{forEach}}, the following would start to warn even though nothing
is wrong, and must be fixed as well:
# All {{camel.variable.*}} keys, as they are not removed when the variables are
set.
# The options of services that are disabled ({{camel.lra.enabled=false}}, and
the same for opentelemetry, opentelemetry2, mdc and telemetryDev).
# When any {{camel.opentelemetry.*}} key is configured (also with
{{enabled=false}}), the {{camel.opentelemetry2.*}} and {{camel.telemetryDev.*}}
properties are not applied at all (telemetryDev is not configured even though
opentelemetry is disabled).
Also:
* Some groups have no warning (metrics, trace, cluster, globalOptions), and
some warnings can never happen (vault, devConsole, beans work on copies of the
properties).
* The warnings should mask the value of sensitive keys, as the
auto-configuration summary does.
This only changes behaviour when {{autoConfigurationFailFast=false}} (with
fail-fast an unknown key fails startup).
_Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
