Should we change the name of the CLI command from 'office365' to 'o365'?
See original GitHub issueCurrently, 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?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
CLI for Microsoft 365 v3
To stay consistent with the new name, we renamed Office 365 CLI to CLI for Microsoft 365. We hope that the new name...
Read more >CLI for Microsoft 365
Using the CLI for Microsoft 365, you can manage your Microsoft 365 tenant and ... To list all available commands, type in the...
Read more >Cross-Platform Administration for Office 365 with Office 365 ...
Office 365 Change Management. Office 365 CLI (“Command-Line Interface”) is a new open source tool that was incubated within the Office ...
Read more >Getting Started With the Office 365 CLI - The Lazy Administrator
Commands in the Office 365 CLI are combined into groups called Command Groups. You can list the commands available in the particular group...
Read more >Command line switches for Outlook 365, 2021, 2019, 2016 ...
Switch Description Works in
/cleanclientrules Starts Outlook and deletes client‑based rules. 2003, 2007, 2010, 2013...
/cleanmailtipcache Removes all MailTips from the cache. 2010, 2013, 2016,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Currently, in package.json we specify
office365as the command name. We could define bothoffice365ando365and see if that would be working with both names.While I prefer having a real name
(office365), if shortened names are the way to go I’m all ok with that.