Nate Pease [X] this is the umbrella ticket for all the command line tool work. If you could link to this ticket with a RelatesTo link that would be good. I don't think this ticket needs to be assigned to you since it's highly likely no work will be done on this directly.

ok

I'm going to set the story points on this ticket to 0 since the work is happening elsewhere.

We probably should shut this ticket down and replace it with explicit tickets for all the items on the list above that have not yet been done – one ticket per subcommand. Nate Pease [X] can you do that and then close this?

Yes, will do. I'm changing the team & epic on this ticket to reflect that it's assigned to me to do that (and so it shows up in my sprint view)

I'm creating a few tickets related to this ticket right now, in order to capture blockers for the "feature parity" milestone.  I will be linking them to this one as "relates to" and at least mostly assigning them to Nate Pease [X] and DAX to start with, as I figure it's a good bet he'll be the one working on them.

I'm working on closing this ticket; I think most of the items listed above have butler CLI commands now. 

• repo subset: I don't think we have command line tool for this, is one still needed?
• manage master calibration collections: we have certify-calibrations, is that one part of this? And we have a ticket to add a CLI cmd for Registry.decertify (DM-26686), is that the other part of what's needed for this? 

These are the rest of the tools listed above, and the butler CLI commands that I think implement them, let me know if I'm wrong about anything.

• repo creation: butler create
• Gen2 repo conversion: butler convert
• skymap registration: butler register-skymap
• visit definition: butler define-visits
• raw ingest: butler ingest-raws
• common Registry queries: query-collections, query-data-ids, query-dataset-types, query-datasets, query-dimension-records
• remove collections butler remove-collections
• remove dataset types that have been registered remove-dataset-type

I'm happy for this umbrella ticket to close.

I think the repo subset one can probably be folded into making transfer-datasets also transfer the dimension it needs. That is effectively moving some code out of execution butler creation into more reusable form. I think that would go a long way to allowing a subset of data to be directly transferred from one repo to another. A completely generic butler exporter command-line is much harder.

We do indeed need a decertify command, we also need a way of listing a calibration collection so that the validation dates can be inspected. I don't think we have a ticket for that but we should create one and block it on whatever ticket Jim thinks is stopping that from working. I think decertify is related in that, like remove-runs, you'd probably want it to report the calibrations that are going to be decertified and possibly tell you the validation ranges for anything that is left (are we going to close up holes in validity? We have to at least report timespans where no calibration is valid).

Of the commands listed in the description, they are either already implemented or child tickets are created and linked to this issue.