From 3ebf4be14efea72284117acd4b7e140c970fca1e Mon Sep 17 00:00:00 2001 From: Croway Date: Wed, 13 May 2026 13:02:31 +0200 Subject: [PATCH] CAMEL-23132: Document ListObjectsV2 migration in upgrade guide --- .../ROOT/pages/camel-4x-upgrade-guide-4_21.adoc | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc index d3b12a318ea02..ccfecdbcc9aa3 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc @@ -307,6 +307,16 @@ previous code path silently produced `null` whenever a route mixed `converse` an calls. If you were not setting the guardrail identifier via header, the endpoint-level `guardrailIdentifier` option continues to work without changes. +=== camel-aws2-s3 + +The `listObjects` operation now uses the `ListObjectsV2` AWS API instead of the deprecated `ListObjects` API. +If you use `pojoRequest=true` with `operation=listObjects`, you must change your request and response types: + +* `ListObjectsRequest` -> `ListObjectsV2Request` +* `ListObjectsResponse` -> `ListObjectsV2Response` + +The non-POJO path (header-based configuration) is updated automatically and requires no changes. + === camel-nats Fixed the JetStream consumer pull subscription mode (which is the default) so that messages are