Skip to content

[Matrix Media Repo] Allow include datastore with none kinds specified #4303

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Pilzinsel64 opened this issue May 8, 2025 · 1 comment
Open
Labels
suggestion This issue is a feature request

Comments

@Pilzinsel64
Copy link

Is your feature request related to a problem? Please describe.
The Matrix Media Repo config allows you to specify datastores in readonly mode by leaving forKind array empty. However, this playbook only includes the datastore in the target yaml config file when kind is specified. That means, it is not possible to move from file datastore to s3 (or reverse) afterwards.

Describe the solution you'd like
Always include both datastores, even if they have no kinds specified.

Describe alternatives you've considered
Add another config option to overwrite the general rule to force-include a datastore even if it has no kinds specified.

Additional context
In my case I want to move from file datastore to s3 and keep file as readonly for the existing media. For this to work at the moment I need to keep at least one kind enabled for file datastore. Otherwise it will be removed from the target yaml config file.
Image

@Pilzinsel64 Pilzinsel64 added the suggestion This issue is a feature request label May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggestion This issue is a feature request
Projects
None yet
Development

No branches or pull requests

2 participants
@Pilzinsel64 and others