Did an experiment with #7 in which subcommands were used to take on presets and other conveniences like parsing URLs. I think the next thing to try is a layered configuration, where defaults can be specified in, say, a file that can be referred to from CLI (i.e., treeherder-dl --preset wpt.yml --revision X). This seems much easier to manage on both dev. and user sides than an ever-expanding set of baked-in presets with their own CLI and potential imperfections.
Did an experiment with #7 in which subcommands were used to take on presets and other conveniences like parsing URLs. I think the next thing to try is a layered configuration, where defaults can be specified in, say, a file that can be referred to from CLI (i.e.,
treeherder-dl --preset wpt.yml --revision X). This seems much easier to manage on both dev. and user sides than an ever-expanding set of baked-in presets with their own CLI and potential imperfections.