-
Notifications
You must be signed in to change notification settings - Fork 29
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
CLI command list #157
Comments
Also include DB migration as a command |
On second thought, maybe
Where the output of each of these commands is just a list of tags or components, one item per line. |
I think this is a better CLI design. This aligns well with what we have now. I can work on this and put up a draft for the same. We can later discuss how this pans out and what needs to be changed. |
@aditim1359 is working on this |
What exactly should "mltrace tags" be doing? Displaying all tags in use for all components? |
Yes -- a tag can be associated with many components. No point in filtering tags by component because we could just call |
Currently we have:
recent
history
trace
We would also like to include:
inspect COMPONENT_RUN_ID
ls tags
ls components
ls components --tag=TAG
ls components --owner=NAME
We can use
get_components_for_owner
andget_components_for_tag
to make thels
commands.The text was updated successfully, but these errors were encountered: