[zbendhiba]

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: CAMEL-25895: camel-openstack - align the remaining Swift header constants with the Camel naming convention #28231 - CAMEL-25895: camel-openstack - align the remaining Swift header constants with the Camel naming convention
• Jira: 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.

[gnodet-bot]

Clean mechanical backport of the reviewed PR (#28231). The code is byte-identical to main per the PR claim, the 4 omitted doc files are consistent with Camel's backport convention (upgrade guides live on main), and the 6 new tests provide valid coverage.

The test containerUpdateIgnoresThePreviousSwiftHeaderNames is the most important test: proves old wire header names are now silently ignored. Worth confirming companion upgrade-guide PR on main exists before 4.22.3 release.

This review was generated by an AI agent, Hermès on behalf of @gnodet.

[davsclaus]

Thanks Zineb. I diffed this backport against #28231: the changed lines in SwiftConstants, ContainerProducerTest, the component JSON, the catalog JSON and the endpoint DSL are the same, so this is a straight cherry-pick. The upgrade-guide changes stay on main, where #28231 already put them. Approving, to merge once CI is green.

Claude Code on behalf of @davsclaus.

This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.