Closed kevmcdonk closed 2 years ago
Forgot to say that I'm happy to work on this myself!
Awesome suggestion and a great spec, thank you @kevmcdonk.
Before you proceed, let's check a few things:
-a, --authorizedAppIds [authorizedAppIds]
authorized
with a z
to follow en-US spelling that we use throughoutIn the future, if there is demand, we could consider extending the command with allowing users to specify apps using their names, which I suspect they'd have readily available comparing to IDs.
Once again, I appreciate the spec and looking forward to your PR.
Working on the PR for this but realised that it needs additional permissions for listing/adding externalconnections (ExternalConnection.ReadWrite.OwnedBy). Where are these defined for the list of permissions that need to be granted on install?
@kevmcdonk we define them in the AAD app that we use for the CLI. For testing you can use a custom AAD app so that you're not blocked. When your PR is ready, we'll review the code and update our AAD app registration.
Ahhh, now I get it. Perfect, thanks for quick response
Usage
This command will allow users to add a new External Connection based on the Microsoft Graph.
search externalconnection add [options]
Description
This command will allow the administrator to create a new external connection for use in Microsoft Search and soon for Viva Topics.
Options
-i, --id <id>
-n, --name <name>
-d, --description <description>
-a, --authorisedAppIds [<appId>]
-o, --output [output]
json,text
. Defaulttext
--verbose
--debug
Additional Information
This is a standard graph command for adding new connections and will be followed up with list and delete.