Federated s3 fixture (GSI-965) #126
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
Pull Request Test Coverage Report for Build 10668642079Details
💛 - Coveralls |
Cito
approved these changes
Sep 2, 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.
Adds the
S3MultiContainerFixtureandFederatedS3Fixturethat were introduced in the SMS. Maintains the same persistent and clean fixture variations that exist with other fixtures.Because the
S3MultiContainerFixturemust know ahead of time about the containers it needs to create, it expects a fixture namedstorage_aliasesto be defined with the same scope. If you try to use the fixture without having defined thestorage_aliasesfixture, you'll get an error.Bumps version to
3.6.0.