davsclaus opened a new pull request, #3171: URL: https://github.com/apache/camel-kamelets/pull/3171
Part of #3170: `ceph-source` and `ceph-sink` get a `forcePathStyle` option. The Ceph Kamelets always put the bucket in the host name of the address (`http://my-bucket.ceph-rgw.example.com:7480/key`), unless `cephUrl` is an IP address. That style works only when the DNS of the gateway has a wildcard name for the buckets, which many Ceph installations do not have. The Ceph Object Gateway always accepts the path style (`http://ceph-rgw.example.com:7480/my-bucket/key`). - **New option:** `forcePathStyle` (boolean, default `false`), passed to the `aws2-s3` endpoint. `aws-s3-source` and `aws-s3-sink` already have it. - **Default unchanged:** the default keeps today's behaviour, so an installation that works now is not affected. - **Descriptions:** the "Good to know" paragraph of both Kamelets says when to set the option. The Ceph Kamelets stay in the catalog instead of being merged into `aws-s3-*`, as decided in #3162. ### Verification Tested against an S3 stand-in (`floci/floci`) on `localhost`, with the SDK request log on: | `forcePathStyle` | Requests went to | Result | |---|---|---| | `true` | `localhost:24566/bucket-true/greeting-true.txt` | Sink wrote the file; source read and deleted it | | `false` (default) | `bucket-false.localhost:24566/greeting-false.txt` | Same as before: the bucket is in the host name | The `false` case works here only because Java resolves `*.localhost`. A gateway whose DNS has no wildcard name for its buckets fails with the host name style, and that is the case the option is for. `./mvnw clean install` passed twice, the first time with `-DskipTests`. _Claude Code on behalf of Claus Ibsen_ 🤖 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]
