You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So that it's consistent with other cli tools, like so kubectl logs my-pod -c my-container -f --tail 100
Proposal
How do you think this should be implemented?
Just changed the flag type from BoolVar and StringVar to BoolVarP and StringVarP respectively.
// StringVarP is like StringVar, but accepts a shorthand letter that can be used after a single dash.
// BoolVarP is like BoolVar, but accepts a shorthand letter that can be used after a single dash.
The text was updated successfully, but these errors were encountered:
Summary
What change you think needs making.
Changed the follow and container flags to BoolVarP and StringVarP respectively in order to support -f and -c shorthands in the command
Motivation
Please give examples of your use case, e.g. when would you use this.
When checking logs of a container... right now we have to write out the whole flag name..
i.e.
argocd app logs my-app --container my-container --follow --tail 100
This is tedious and inconsistent with other similar utilities like kubectl, docker, etc.
Should be like so..
argocd app logs my-app -c my-container -f --tail 100
So that it's consistent with other cli tools, like so
kubectl logs my-pod -c my-container -f --tail 100
Proposal
How do you think this should be implemented?
Just changed the flag type from BoolVar and StringVar to BoolVarP and StringVarP respectively.
// StringVarP is like StringVar, but accepts a shorthand letter that can be used after a single dash.
// BoolVarP is like BoolVar, but accepts a shorthand letter that can be used after a single dash.
The text was updated successfully, but these errors were encountered: