Short alias in CLI

[NissesSenap]

/kind feature

Which functionality do you think we should add?

Add short aliases for CLI commands. Currently I have to type odo list I would like to be able to type odo ls

Why is this needed?

Currently the CLI is forcing the developers to be very verbose when typing commands which takes time.
I have given a example above with list vs ls.
There is probably more "standard" aliases that could be implemented in the cli to make life easier for developers.

[kadel]

Hi, @NissesSenap to save some typing you can also use autocompletion, this is much more useful than aliases.
If you execute source <(odo utils terminal bash) (or source <(odo utils terminal zsh) if you use ZSH) you will be able to do odo li<tab>. Autocompletion should also work for flags. To make it persistent you add the command to your .bashrc .zshrc.

[NissesSenap]

Thanks for the tip @kadel I have done this and as you say it saves some time but I guess me and most developers today is used of doing "ls" or "get" when you want a list of things within kubernetes.

I haven't had time to look at the odo code but I assume it uses a cli framework like cobra or something similar so adding aliases shouldn't be a super big feature but my two cents is that it will make life easier for developers.

[kadel]

Yes, we use Cobra, aliases are not a problem. We are actually already doing it.
In reality odo list is already an alias for odo component list :-)

We will look into making commands a little bit shorter and use common shortcuts that people are used to.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.