Skip to content

Audit follow-up: decide on deprecated Camel components without drop-in replacements (paho/MQTTv3, splunk, json-patch) #2890

Description

@oscerd

Background

The 4.21.0 deprecation audit (#2830, fixed in #2886) removed the deprecated endpoint options it found (pulsar-sink / slack-sink). It also found three Kamelets using deprecated Camel components that have no safe drop-in replacement, so they were intentionally left for a maintainer/PMC decision rather than a breaking change.

Components needing a decision

  • json-patch-actioncamel:json-patch (deprecated): no replacement component exists in the Camel 4.21 catalog.
  • mqtt-source, mqtt-sinkcamel:paho (MQTT v3, deprecated): the only sibling is camel:paho-mqtt5 (MQTT v5 — a protocol change), and mqtt5-source / mqtt5-sink already provide v5. Migrating would break v3 users or duplicate the v5 Kamelets.
  • splunk-sink, splunk-sourcecamel:splunk (deprecated): splunk-hec is publish-only and config-incompatible; splunk-source (search) has no HEC equivalent, and splunk-hec-sink already covers HEC publishing.

Options per component

  1. Deprecate the affected Kamelet(s) (e.g. label/annotate, document) and steer users to alternatives where they exist.
  2. Accept the behavioural change (e.g. migrate mqtt-* to MQTT v5) — needs an upgrade-guide note.
  3. Keep as-is until the component is actually removed upstream in Camel, then revisit.

No action is required in the catalog until Camel removes these components; this issue tracks the decision so the deprecations are not forgotten.

AI-generated by Claude Code on behalf of Andrea Cosentino (@oscerd)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions