remove S3 legacy CI job #11743
Merged
remove S3 legacy CI job #11743
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bentsku
added
area: ci
bentsku
requested review from
alexrashed,
dfangl and
dominikschubert
as code owners
alexrashed
approved these changes
Oct 25, 2024
Member
alexrashed
left a comment
alexrashed
left a comment
There was a problem hiding this comment.
Great to see that we clean up here as we really don't need the regression testing of a provider which will not even be contained in the next release anymore. 🧹 💯
This was referenced Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
As we are planning to remove the S3 legacy implementation, we can already remove the S3 CI job, as I'd like to setup a job for the DynamoDB(Streams) v2 provider, and the CI service-specific job landscape is getting crowded.
Changes