New-VcConnector manfest change fix

[gdbarron]

• Update New-VcConnector and Set-VcConnector to support the manifest structure change

[gdbarron]

Successfully tested New-VcConnector and Set-VcConnector commands.

Note that when using an existing connector name, an http "500" error is returned, but no clear error pointing to the problem.

New-VcConnector : {"errors":[{"code":16004,"message":"Unable to create new plugin."}]}
At line:1 char:1
+ New-VcConnector -ManifestPath C:\tmp\manifest.create.json -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [New-VcConnector], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,New-VcConnector

Thanks for this feedback. This is what the api is giving us so perhaps we can suggest they enhance the error message.

[astro2000j]

Successfully tested New-VcConnector and Set-VcConnector commands. Note that when using an existing connector name, an http "500" error is returned, but no clear error pointing to the problem.

New-VcConnector : {"errors":[{"code":16004,"message":"Unable to create new plugin."}]}
At line:1 char:1
+ New-VcConnector -ManifestPath C:\tmp\manifest.create.json -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [New-VcConnector], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,New-VcConnector

Thanks for this feedback. This is what the api is giving us so perhaps we can suggest they enhance the error message.

That’s why I chose to approve rather than block it based on the return. Better to have the endpoint supply the reason than taking the time to work out the logic on our side.