Add extension command module

[calebkiage]

Overview

Adds a command to manage 3rd party extensions in the cli

Demo

(msgraph-cli) > ./mg extension list
[]

(msgraph-cli) >./mg extension show
ERROR: the following arguments are required: --name/-n

TRY THIS:
az extension show --name MyExtension
Show an extension. (autogenerated)

az extension list
List the installed extensions. (autogenerated)

https://docs.microsoft.com/en-US/cli/azure/extension#az_extension_show
Read more about the command in reference docs

(msgraph-cli) >./mg extension list-available
[
  {
    "experimental": false,
    "installed": false,
    "name": "mail_beta",
    "preview": true,
    "summary": "Microsoft Azure Command-Line Tools Mail Extension",
    "version": "0.1.0"
  }
]

Testing Instructions

• Run the command ./mg extension --help to see the available commands
• Run any of the commands to test.

Microsoft Reviewers: Open in CodeFlow

[jobala]

@MIchaelMainer I prefer ./mg extension because it provides an interface similar to Azure CLI's and most of our users will be familiar with how Azure CLI works. I would tradeoff the confusion with consistency with Azure CLI.

[MIchaelMainer]

In terms of consistency, with the same concept in Azure, yes, keeping the name would provide consistency in the CLI experience. If we changed the name, it would still be functionally consistent, but without the same command group name as experienced in the Azure CLI. We also have to consider the term extension across all of Microsoft Graph:

https://docs.microsoft.com/en-us/search/?scope=graph&view=graph-rest-1.0&terms=extension

There are a lot of hits on extension.

We need to think about a future where we generate CLI code snippets and inject into the documentation. We also need to consider the impact on search indices when customers search on the term extension. Extension is already an overloaded term in Microsoft Graph (and software development in general). By not disambiguating it here, we increase the potential for confusion across the CLI, documentation, and pretty much anywhere else that Microsoft Graph based content is indexed or used.

Case in point: if the folks who created the schema extension feature called it extension, we would have had to disambiguate the term at this point. But they did the right thing and disambiguated the term so that we can have this discussion 😄. There is little ambiguity by calling it cli-extension.