rich7420 opened a new pull request, #10966: URL: https://github.com/apache/ozone/pull/10966
## What changes were proposed in this pull request? The goal of this task is to provide a Testcontainers module, so JVM projects can start a single-node Ozone with S3 Gateway in integration tests, the same way they use the MinIO or LocalStack modules. Ozone has no Testcontainers module yet (org.testcontainers is not used anywhere in the repo). Motivated by the container-based test-framework interest (e.g. Trino) raised on [HDDS-14893](https://issues.apache.org/jira/browse/HDDS-14893). Scope=> New published module ozone-testcontainers under hadoop-ozone. An OzoneContainer (extends GenericContainer) that runs single-node Ozone with S3 Gateway by wrapping the all-in-one image (apache/ozone:<tag>-all-in-one, from [HDDS-14452](https://issues.apache.org/jira/browse/HDDS-14452) / ozone-docker#49). Accessors mirroring the MinIO/LocalStack modules: getS3Endpoint(), getAccessKey(), getSecretKey(), getRegion(). Wait strategy on the S3 Gateway port (9878); a smoke test doing S3 create/put/get with AWS SDK v2 (path-style + static credentials), skipped when Docker is unavailable. A Note here=> uses the all-in-one image today; a cleaner `ozone local run` based image ([HDDS-15087](https://issues.apache.org/jira/browse/HDDS-15087)) would be a future improvement, not a blocker. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-16077 ## How was this patch tested? https://github.com/rich7420/ozone/actions/runs/31161526340 -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
