Cli-microsoft365: New command: Sync solution package to Microsoft Teams

Created on 19 Mar 2019  路  14Comments  路  Source: pnp/cli-microsoft365

Usage

spo app synctoteams [options]

Description

Sync Sync solution package to Microsoft Teams

Options

| Option | Description |
| ----------------------- | ----------------------------------------- |
| -i, --id <id> | The ID of the solution package to sync to Microsoft Teams |

Additional Information

POST /_api/web/tenantappcatalog/SyncSolutionToTeams(id={itemId})

The itemId passed to the REST API is the ID of the solution package list item and not the id of the solution package. The command should accept the ID of the solution package and resolve the corresponding list item id.

Docs: Synchronize a solution to the Microsoft Teams app catalog

good first issue new feature not supported

All 14 comments

I will work on this. Lets hope the api works now.

Ok, the banch is here, but I could not make it work with access token. Seems the only way it works is by using cookie auth or I am missing something. I opened conversation already. I am waiting for response now.

No response from the Microsoft guys when that can be fixed. This command might not fly soon.

If it's not possible, then we put it on-hold until we know more. It is what it is.

Yes, that is correct. There is a way to still execute the command where we have to build cookie by ourselfs and send it with the request (this is how it is being done in the C# PnP-Core lib), but I would not want to go that path.

You're right 馃憤 Let's close this issue for now and reopen when anything changes.

@VelinGeorgiev did you receive a reply on this from MS? I've just hit this issue 馃槵

I asked. They did not answer.

Damn... out of interest did you create an sp-dev-docs issue or support ticket?

Nope. Feel free to do so..

According to the docs, the REST API should support using access token. Shall we give it another try?

Updated OP to use new template, add new supporting documentation and opened up.

Just had another look. Seems that docs are incorrect. Bearer token is still not supported

Since this is not supported by the API, let's close this issue for now and reopen in the future when this becomes possible.

Was this page helpful?
0 / 5 - 0 ratings