Add support for custom backup provider patterns #84
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.
Overview
This PR adds the ability to extend backup providers with custom patterns using environment variables, making the tool more flexible for users who have specific container naming conventions.
Features
Implementation
Users can now add custom container patterns to the existing backup providers by setting environment variables in the format
CUSTOM_BACKUP_PROVIDER_<provider_name>_PATTERNS=pattern1,pattern2,...
. This allows for extending the patterns list without modifying the code.For example:
Documentation
Updated the README.md with:
Testing
Use Case
This addresses the use case where users need to back up databases with container patterns not included by default, such as "immich-app/postgres".