goutamadwant opened a new pull request, #12302:
URL: https://github.com/apache/seatunnel/pull/12302
### Purpose of this pull request
Follow up on #12287 by updating the remaining Docker Hub MinIO image
reference in `S3FileConnectDryRunIT`, introduced by #12242.
The fixture still uses `minio/minio:RELEASE.2024-06-13T22-53-53Z`. Pulling
this image fails with `pull access denied`, preventing the MinIO container from
starting and the S3 dry-run tests from executing. This is a test-infrastructure
failure before connector assertions run.
This patch changes the image to
`quay.io/minio/minio:RELEASE.2024-06-13T22-53-53Z`.
- Changes only the registry reference in one test fixture.
- Preserves the pinned MinIO release, container configuration, and existing
assertions.
- Aligns this fixture with the registry migration in #12287.
- Does not increase timeouts, disable tests, or change production code.
### Does this PR introduce _any_ user-facing change?
No. S3 connector behavior, configuration, dependencies, and compatibility
are unchanged. This change restores the existing integration-test fixture.
### How was this patch tested?
- Reproduced the Docker Hub image pull failure.
- Successfully pulled the same pinned release from Quay.
- Verified that the Quay image provides AMD64 and ARM64 manifests. This is
manifest verification, not runtime testing on both architectures.
- Ran all six existing `S3FileConnectDryRunIT` tests against a real MinIO
container using Java 11: **6 passed, 0 failures, 0 errors, 0 skipped**.
- Ran Spotless and the selected module's dependency-reactor verification
successfully.
The existing tests exercise the S3 source factory metadata and connectivity
contract without submitting a SeaTunnel job. No new tests were added because
the patch only corrects the image location required by those tests.
Focused verification command, with Java 11 and Docker available:
```bash
./mvnw -B \
-pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-file-s3-e2e \
-am verify \
-Dskip.ui=true \
-Dlicense.skipAddThirdParty=true \
-DskipUT=true \
-DskipIT=false \
-Dit.test=S3FileConnectDryRunIT \
-Dit.failIfNoSpecifiedTests=false \
'-Dsurefire.jvm.args=-Dfile.encoding=UTF-8 -Dapi.version=1.44'
```
The Docker API version override was used for local Docker 29 compatibility;
it is not a repository change.
### Check list
The conditional items below are not applicable to this test-fixture-only
change. No JAR, documentation, compatibility, connector registration,
distribution, or plugin configuration changes are introduced. The existing E2E
tests were rerun successfully.
* [ ] If any new Jar binary package adding in your PR, please add License
Notice according [New License
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)
* [ ] If necessary, please update the documentation to describe the new
feature. https://github.com/apache/seatunnel/tree/dev/docs
* [ ] If necessary, please update `incompatible-changes.md` to describe the
incompatibility caused by this PR.
* [ ] If you are contributing the connector code, please check that the
following files are updated:
1. Update
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
and add new connector information in it
2. Update the pom file of
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
3. Add ci label in
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
4. Add e2e testcase in
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
5. Update connector
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)
--
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]
