CAPA: Request aws-ebs-csi-driver v3.0.0.
#1528
Merged
Conversation
This file contains 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
Gacko
changed the title
Gacko
changed the title
aws-ebs-csi-driver v3.0.0.
Gacko
approved these changes
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Checklist
Triggering E2E tests
To trigger the E2E test for each new Release added in this PR, add a comment with the following:
/run releases-test-suitesIf your release is a new patch release for an older major release, you need to specify the previous release for use in upgrade tests, for example for
25.1.2(exists) to25.1.3(added in your PR):/run releases-test-suites PREVIOUS_RELEASE=25.1.2If your release is a new minor release for an older major release, e.g.
25.3.0(exists) to25.4.0(added in your PR), it works the same way:/run releases-test-suites PREVIOUS_RELEASE=25.3.0You can also limit which tests are run:
/run releases-test-suites TARGET_SUITES=./providers/capa/standardIf you want to trigger conformance tests, you can do so by adding a comment similar to the following:
/run conformance-tests PROVIDER=capa RELEASE_VERSION=29.1.0For more details see the README.md.