luigidemasi opened a new issue, #122:
URL: https://github.com/apache/camel-kit/issues/122
Two shipped guides state that Forage environment variables and system
properties can only address the default-bean key form and cannot target a named
bean's key:
- `camel-kit-core/src/main/resources/skills/shared/forage.md`, paragraph
**Configuration precedence**: "Env vars and system properties only address the
DEFAULT-bean key form (no name segment) — they cannot target a NAMED bean's key
(`forage.myDb.jdbc.url`). Override a named bean's config through the properties
file."
-
`camel-kit-core/src/main/resources/skills/camel-test/guides/test-configuration.md`,
note **Forage override channels**: the same restriction, for CI overrides.
Forage 1.6.1 (the version mapped to Camel 4.22.1 in
`distribution.properties`) does not have this limitation. In
`io.kaoto.forage.core.util.config.ConfigModule`, `asNamed("myDb")` builds the
full property name with the prefix inserted after `forage.`
(`forage.myDb.jdbc.url`) and `envName()` derives `FORAGE_MYDB_JDBC_URL` from
it; `ConfigStore` reads both. A JVM probe against the published
`forage-core-common:1.6.1` artifact confirms it:
```
envName=FORAGE_MYDB_JDBC_URL
propertyName=forage.myDb.jdbc.url
resolved=jdbc:probe:env # environment set, system property set:
environment wins
resolved=jdbc:probe:system # only the system property set
```
Both statements were introduced together on 2026-07-07 (`96046345`,
`f3942be5`). As written they steer the generated instructions, and anyone
reading the guides, toward properties-file edits that are not needed in
deployment or CI.
Expected fix: describe the named forms (`FORAGE_<NAME>_<DOMAIN>_<PROP>` and
`-Dforage.<name>.<domain>.<prop>=...`) with the same precedence as the default
form, in both guides. Shipped-asset change, so the full reactor build and
`ResourceConsistencyTest` / `BeanConstructionGuidanceTest` apply.
Website impact: not required. The documentation page on Forage already
describes the verified behaviour.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
