Forage Configuration Catalog

Forage (io.kaoto.forage) creates infrastructure beans from forage.<name>.<domain>.* properties and registers each bean in Camel as #<name>. Camel-Kit uses its cached catalogs as the source of truth for supported factories, runtime dependencies, and property keys.

Availability and Version Streams

camel-kit init records forage.version and caches the matching catalogs under .camel-kit/.cache/forage/{version}/. If no version is mapped or the cache is absent, Camel-Kit skips the Forage rung instead of inventing configuration.

The version mappings in distribution.properties are authoritative.

Configuration Ladder

For every datasource, connection factory, AI service, CXF endpoint, or other infrastructure need, Camel-Kit stops at the first supported option:

1. Forage catalog coverage — emit catalog-verified forage.* properties and reference the registered bean as #<name>.
2. Camel component properties — use camel.component.<scheme>.* scalar properties verified by Camel MCP.
3. Hand-wired bean — use camel.beans.<name>=#class:... only when the first two rungs cannot construct the required object, with a one-line reason comment.

Example datasource:

forage.myDb.jdbc.db.kind=postgresql
forage.myDb.jdbc.url=jdbc:postgresql://{{db.host}}:{{db.port}}/{{db.name}}
forage.myDb.jdbc.username={{db.username}}
forage.myDb.jdbc.password={{db.password}}

A route can then use sql:...?dataSource=#myDb.

Catalog Checks

The cache contains forage-catalog.json for factories, component coverage, bean kinds, and runtime GAVs, plus forage-configuration-catalog.json for property names and types. Skills query only the needed slice:

CACHE=.camel-kit/.cache/forage/${FORAGE_VERSION}

# Factory and bean-kind coverage
jq -r '.factories[] | .name + ": " + ([.beansByFeature[]?.beans[]?.name] | join(", "))' "$CACHE/forage-catalog.json"

# Components served by each factory
jq -r '.factories[] | .name + " -> " + (.components | join(", "))' "$CACHE/forage-catalog.json"

# Runtime dependency for a factory
jq -r '.factories[] | select(.name=="DataSource") | .variants.base.gav' "$CACHE/forage-catalog.json"

# Property keys for a module
jq -r '.modules[] | select(.artifactId=="forage-jdbc-common") | .configEntries[].name' "$CACHE/forage-configuration-catalog.json"

Named-bean keys are normalized to the catalog’s default-bean form before validation: forage.myDb.jdbc.url is checked as forage.jdbc.url. An unknown forage.* key, or an unexplained hand-wired bean with a Forage equivalent, fails /camel-validate; a hand-wired bean with only a scalar component-property alternative produces a warning.