davidzollo opened a new pull request, #11828: URL: https://github.com/apache/seatunnel/pull/11828
## What does this PR do? This follow-up hardens the all-connectors shard contract that was introduced by #11291. It keeps the regular `sub_it_module` path strict by failing fast when a dedicated suite disappears from the full module list, and it adds regression coverage that now checks: - the exact surviving regular-shard module set - the one-time-only assignment contract - the workflow coverage for suites that are intentionally excluded from regular all-connectors shards ## Why is this follow-up scoped narrowly? The PR-scoped `sub_update_it_module` path is intentionally left unchanged. The current backend workflow has eight updated-modules shards, but it does not have a dedicated Iceberg/HBase lane for that path. Filtering those suites there would drop PR-scoped coverage instead of deduplicating it. ## Verification - `./mvnw spotless:apply` - Independent maintainer review on the final diff Local unit/integration execution was not run here because this task follows the repo workflow we are using for SeaTunnel CI follow-up fixes: formatting locally, and functional validation on GitHub CI. -- 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]
