Support for multiple S3 backends#73
Merged
cloudlena merged 1 commit intocloudlena:mainfrom Nov 26, 2025
Merged
Conversation
This was referenced Nov 25, 2025
Owner
|
Amazing! Many thanks, @enzodjabali! |
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.
Add support for multiple S3 backends with environment-based configuration.
This PR introduces the ability to configure and manage multiple S3 backends within a single instance of s3manager. Users can define multiple S3 instances via environment variables prefixed with numeric identifiers (e.g. 1_NAME, 1_ACCESS_KEY_ID, 2_NAME, etc.), enabling dynamic management of multiple S3-compatible storage providers or accounts.
Key changes include:
Cheers ;)