-
Notifications
You must be signed in to change notification settings - Fork 39
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
Unixify user interface #38
Labels
Comments
flosell
added a commit
that referenced
this issue
May 1, 2018
flosell
added a commit
that referenced
this issue
May 1, 2018
… passed in as stdin to unixify CLI interface #38
flosell
added a commit
that referenced
this issue
May 1, 2018
Done. Piping has a performance impact but is ok when traded off against the flexibility of the interface . Created #44 to work on inefficiencies. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the CLI interface is organized around a very specific workflow and is convenient if you are using that specific workflow. Everything that's not that workflow is hard (e.g. generating a policy for a very specific selection of events, only fetching and printing certain events and then post-processing them with another tool (e.g.
jq
)).For this reason, it would be nice if the trailscraper commands behaved more according to the Unix philosophy and only do one thing.
Proposal:
trailscraper generate-policy --from "one day ago"
becomestrailscraper select --from "one day ago" | trailscraper generate
Concerns:
Performance impact of piping?
The text was updated successfully, but these errors were encountered: