zbendhiba opened a new pull request, #28280: URL: https://github.com/apache/camel/pull/28280
## Backport of #28231 to `camel-4.22.x` Cherry-pick of #28231 (`3ef68e407da3`) onto `camel-4.22.x`, shipping in **4.22.3**. - **Original PR:** #28231 - CAMEL-25895: camel-openstack - align the remaining Swift header constants with the Camel naming convention - **Jira:** [CAMEL-25895](https://issues.apache.org/jira/browse/CAMEL-25895), fixVersions 4.18.6, 4.22.3, 4.24.0 ### What this carries The five functional files of the original commit, applied with no change: | File | | |---|---| | `SwiftConstants.java` | the four header constants take their `CamelOpenstackSwift*` values | | `ContainerProducerTest.java` | six new tests for the container options path, which had no coverage | | `openstack-swift.json` (component + catalog) | regenerated metadata | | `SwiftEndpointBuilderFactory.java` | regenerated Endpoint DSL header accessors | The Java field names are unchanged, so routes using the constants symbolically keep working. The request Camel sends to Swift is unchanged: openstack4j builds the `X-Container-*` wire names itself from `CreateUpdateContainerOptions`, so the Exchange header key never reaches Swift. ### What this does not carry, and why The original commit also touched `design/headers.adoc` and three upgrade guides. None of them is carried here: the project keeps the upgrade guides for every version on `main`, where they act as the canonical history across releases. `design/headers.adoc` does exist on this branch, but the design notes are kept on `main` for the same reason. The 4.22.3 upgrade-guide note is added on `main` instead, in the companion PR, under `== Upgrading from 4.22.2 to 4.22.3`. ### Mechanical-port check The code is a byte-identical port: the resulting `ContainerProducerTest.java` is identical to `main`, `ContainerProducer.java` is identical on this branch and on `main`, and the changeset is identical to the `camel-4.18.x` / `camel-4.22.x` sibling backport. The only conflict resolution was removing the doc files that do not exist on this branch, so a `gh pr diff` comparison against #28231 will show those doc hunks as the difference. No reviewers are requested, per the project's backport rule; the code went through review on #28231. -- 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]
