Cli-microsoft365: Should we change the name of the CLI command from 'office365' to 'o365'?

[waldekmastykarz]

Currently, you start the CLI by typing office365 in the terminal. That launches the immersive CLI. When in the future the CLI will support a non-interactive/-immersive mode, it would mean that you have to prefix each command with office365, eg.:

$ office365 spo tenant cdn set -e true
$ office365 spo tenant cdn origin set -o */CDN
...

We could change the name of the CLI to o365 to shorten the name, similarly like the Azure CLI uses az as their prefix:

$ o365 spo tenant cdn set -e true
$ o365 spo tenant cdn origin set -o */CDN
...

What do you think @andrewconnell, @wictorwilen, @estruyf?

[andrewconnell]

Can you alias it? If so I'd do that...

If you can't, I'd look pretty close to what MSFT does... are things spelled out? If so, I'd do that. IMHO, I'd go with either office or office365. Why? You don't go to https://portal.o365.com.

[waldekmastykarz]

Currently, in package.json we specify office365 as the command name. We could define both office365 and o365 and see if that would be working with both names.

[estruyf]

Alias seems to be a good option. o365 is the one I will be using, but it makes sense to have both.

[wictorwilen]

While I prefer having a real name (office365), if shortened names are the way to go I'm all ok with that.

[waldekmastykarz]

Cool, let me have a look if we can have two aliases.