oscerd opened a new pull request, #23889: URL: https://github.com/apache/camel/pull/23889
## Backport of #23886 Cherry-pick of #23886 (squash commit `72d13bd13fb`) onto `camel-4.18.x`. - **Original PR:** apache/camel#23886 โ CAMEL-23630: add HeaderFilterStrategy to camel-dapr - **Original author:** @oscerd - **Approved by:** @davsclaus - **Target branch:** `camel-4.18.x` (4.18.3-SNAPSHOT) ### What this backports Adds `DaprHeaderFilterStrategy` (exposed via `DaprComponent` / `DaprEndpoint` as the standard `headerFilterStrategy` option) and stops the `dapr-pubsub` consumer from copying the inbound CloudEvent's `pubsubName` / `topic` into the `CamelDaprPubSubName` / `CamelDaprTopic` headers. Those two constants are producer-direction routing headers that `DaprConfigurationOptionsProxy` reads back and prefers over the endpoint-configured destination, so a `from(dapr-pubsub).to(dapr-pubsub)` route incorrectly carried the inbound destination into the producer hop. The remaining CloudEvent metadata headers are unchanged. ### Backport notes - **Upgrade-guide entry omitted by design.** The original PR added a note to `camel-4x-upgrade-guide-4_21.adoc`, which does not exist on `camel-4.18.x`. Per project policy, upgrade-guide entries live on `main`; a matching `camel-4x-upgrade-guide-4_18.adoc` entry on `main` will follow so the 4.18.x line is documented. - **Clean cherry-pick:** all 12 code/generated files applied without conflict; only the `4_21` upgrade-guide hunk was dropped. - **Validated locally:** `mvn -pl components/camel-dapr clean install` on a `camel-4.18.x` worktree โ BUILD SUCCESS, 52 tests pass (incl. `DaprPubSubConsumerTest`), no regenerated-file drift. --- _Backport prepared by Claude Code on behalf of Andrea Cosentino_ ยท ๐ค Generated with [Claude Code](https://claude.com/claude-code) -- 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]
