Restore S3 dry-run MinIO integration tests
Updated the final stale MinIO Docker Hub reference in the S3 connectivity dry-run fixture to MinIO's Quay registry while preserving the pinned release and all existing assertions.
apache/seatunnel · #12302
Test-infrastructure reliability fix
SeaTunnel's S3 connectivity preflight tests can run again after Docker Hub stopped serving the pinned MinIO image.
Problem
The test fixture still pulled `minio/minio` from a Docker Hub repository that no longer served anonymous images. Container startup failed before any S3 dry-run assertion could execute, leaving this integration path broken after the broader registry migration.
Approach
Changes the fixture's registry reference to `quay.io/minio/minio` for the same pinned release. Because the fixture uses a generic Testcontainers container, no compatible-substitute declaration or production-code change is required.
Impact and scope
- Restores six real-service integration tests for S3 object, prefix, credential, and connectivity validation.
- Closes the last remaining stale `minio/minio` reference missed by the project-wide registry migration.
- Keeps the container release, configuration, assertions, connector behavior, APIs, and dependencies unchanged.
Validation
- Reproduced the Docker Hub pull failure, pulled the same pinned release from Quay, and verified AMD64 and ARM64 image manifests.
- All six existing `S3FileConnectDryRunIT` cases passed against a real MinIO container on Java 11; Spotless and dependency-reactor verification also passed.
- A SeaTunnel collaborator approved the focused fix, the final Build check passed, and the GitHub-verified merge commit credits Goutam Adwant. Runtime testing was performed on one local architecture; multi-architecture evidence is manifest-only.