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

update 'run' parameter #77

Open
senthil10 opened this issue Mar 19, 2015 · 3 comments
Open

update 'run' parameter #77

senthil10 opened this issue Mar 19, 2015 · 3 comments

Comments

@senthil10
Copy link
Member

As of now --run accepts only path, could be useful that it can be a file as well (with list of runs to archive).

@guillermo-carrasco : Would it be a over kill ?

@guillermo-carrasco
Copy link

It does not accept only a path, you can specify only a filename, and then it will prepend the storage/archive_dirs directory specified in the configuration, have a look here.

@senthil10
Copy link
Member Author

Yes, I am aware of that :) When I meant PATH I really meant like we can give only one run for example like

taca storage --days 2 --run 150224_D00134_0180_AC6AHVANXX archive --backend swestore

But what this issue is about to have some thing like this

taca storage --days 2 --run runs_to_archive.txt archive --backend swestore

cat runs_to_archive.txt
150202_D00134_0173_BHB6WVADXX
150204_D00134_0174_AHB6H1ADXX

So would that be useful ? or an over kill ? :)

@guillermo-carrasco
Copy link

aha I see, no, it may be useful and you're not adding extra options, which is nice. Just have to add the piece of code that determines if it's a text file and read it if so.

Go for it!

Just, don't forget to document all of this somehow, in the package docs for example, or it will be forgotten soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants