Repository navigation
Fix S3 bucket mappings for vacuum integration tests - #243
Closed
Vlasdislav wants to merge 1 commit into
Closed
Vlasdislav wants to merge 1 commit into
Vlasdislav wants to merge 1 commit into
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
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.
Superseded by open-gpdb/gpdb#444. The mappings belong in the existing gpdb test configuration, so no additional yproxy workflow step is needed.
After switched branch in CI in yezzey for gpdb open-gpdb/gpdb#437, we need usage some tablespaces.
The yezzey integration test
yezzey-vacuum-garbagecreates tablespacesvacuum_garbage_tab1andvacuum_garbage_tab2, but the gpdb test configuration only mapstab1andtab2to S3 buckets. Inserts into the new tablespaces fail withfailed to complete external storage interactionbecause yproxy cannot resolve their buckets.Add mappings to the existing
gpyezzey2andgpyezzey3buckets before building the integration image. Keep the existing mappings and credentials.