Skip to content
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

Backup Without Snapshot Creation & Deletion #851

Open
PACordonnier opened this issue Feb 6, 2025 · 0 comments · May be fixed by #852
Open

Backup Without Snapshot Creation & Deletion #851

PACordonnier opened this issue Feb 6, 2025 · 0 comments · May be fixed by #852

Comments

@PACordonnier
Copy link

PACordonnier commented Feb 6, 2025

Description

It would be useful to have an option to run the backup feature in Medusa without automatically creating a snapshot. Instead, I would like to use Medusa solely for uploading an existing snapshot to the backup repository. Additionally, I would prefer Medusa not to delete the snapshot after the backup process is completed.

Use Case

I have my own workflow for creating snapshots, and I want to leverage Medusa only for the upload process. Currently, it seems Medusa always takes a new snapshot and deletes it afterward, which doesn’t align with my needs.

Possible Solution

Would it be possible to introduce an option (e.g., --no-snapshot) that allows users to specify an existing snapshot for upload instead of creating one? Additionally, a flag like --keep-snapshot could be useful to prevent automatic deletion.

Notes

I’m not an expert in Medusa, so I might be misunderstanding how it works. If there’s already a way to achieve this, I’d appreciate any guidance.

Thanks for your time and for maintaining this project!

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: MED-123

@PACordonnier PACordonnier linked a pull request Feb 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant