Disable Wasabi as a Storage Provider in Preservation Services#187
Open
Disable Wasabi as a Storage Provider in Preservation Services#187
Conversation
diamondap
reviewed
Dec 17, 2025
Member
diamondap
left a comment
diamondap
left a comment
There was a problem hiding this comment.
The existing changes look fine, but integration tests fail with this message:
Config is missing BucketWasabiOR
I think there's still code in models/common/config.go that does a sanity check to ensure the app has all the config data it needs to start. You need to remove the checks for Wasabi config data, which is no longer required.
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
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.
Removes references to Wasabi in preservation-services.
Test fixtures are staying in place for now.