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

Option to provide fixed name the output of the backup app #281

Open
landmanbester opened this issue Jun 20, 2023 · 1 comment
Open

Option to provide fixed name the output of the backup app #281

landmanbester opened this issue Jun 20, 2023 · 1 comment

Comments

@landmanbester
Copy link
Collaborator

Describe the problem that the feature should address
Currently the backup app uses a time stamp to set the default name of the output. This makes it hard to know the name of the output when reusing them (for example as an output of a stimela recipe step). Also, if you are like me and don't use the zarr_dir to reflect the state of the MS when the backup occurred, it's difficult to remember which backup to use to get back to a particular state.

Describe the solution you'd like
It would be useful if one could pass in a fixed name in addition to zarr_dir to provide a more human-proof backup solution. Datetime can still be the default.

Describe alternatives you've considered
I can't see any sane alternatives in the stimela use case above but open to suggestions

@JSKenyon
Copy link
Collaborator

This is on my to-do list - I actually want to make it an entirely separate package which QuartiCal simply installs. Part of that change would be to give it a more fully fledged CLI, including something like newpackagename list which can inspect the contents of a directory and print some human readable output. It would also support adding comments to the backups to make this simpler e.g. newpackagename backup -m "Some informative string." otherargs

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

No branches or pull requests

2 participants