Can not install extensions via commandline #141

jhandel · 2016-08-19T21:00:44Z

This command used to work with VSTS with no problems...

tfx extension install --token [My Persona Access Token] --service-url https://marketplace.visualstudio.com/ --publisher [My Publishing Account] --extension-id [My Extention] --accounts [target account]

(values removed to protect the innocent)

I hadn't used it for a few weeks, but now all I receive is the following error :
[target account]: [Failed: Error: Failed Request: Forbidden(403) - Access Denied: [user name] needs the following permission(s) to perform this action: Edit instance-level information]

Nothing was changed in our account in VSTS nor was anything changed in the release that uses this code.. I have also tried this manually with the same error..

I have looked into VSTS online and can't find anywhere to set or confirm if Edit instance-level information has been edited... Also I can still install extensions via the marketplace (even the extension I had previously automated the installation of).

Thanks

T-Hugs · 2016-08-19T21:02:20Z

Is it possible your token has expired?

jhandel · 2016-08-19T21:06:29Z

Nope that is a brand new token (thought of that, revoked and created a new token) and the token successfully publishes extensions with no changes to those steps...

T-Hugs · 2016-08-19T21:09:44Z

Interesting. I was able to repro this. Someone must have changed something important without telling me :) I'll have a look next week. Sorry for the inconvenience!

jhandel · 2016-08-19T21:13:11Z

Thanks for looking into it so quickly.. Have a great weekend.. hopefully it won't be too nasty a fix for the team.

jdshkolnik · 2016-08-22T22:33:07Z

Whew; it's not just me.

brunopssp · 2016-08-24T02:57:01Z

The exactly same thing with me.

T-Hugs · 2016-08-24T12:41:55Z

Just a quick update - we briefly looked into this issue and so far don't know what the cause is. I wasn't able to reproduce it on my local dev instance, only against production. Our team is quite busy this week with RC2, so we probably won't be able to really investigate until next week. Sorry for the delays! You should still be able to use Install through the web UI.

T-Hugs · 2016-09-06T17:09:58Z

I have the fix for this - I'm wrapping things up now but I have to leave early today - I will try to push this evening.

T-Hugs · 2016-09-07T03:00:18Z

Ok, hopefully this is fixed in e38bbdb. Let me know if you run into any issues. Thanks.

jmezach · 2016-09-07T07:40:10Z

Not sure if this is related to this fix, but I tried to run my release definition today which shares an existing extension with another account and then tries to install it, but now I'm getting the following error:

2016-09-07T07:31:16.4879327Z [command]C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\1.104.1\tasks\ShareExtension\0.7.3\node_modules\.bin\tfx.cmd extension share --token ******** --service-url https://marketplace.visualstudio.com/ --publisher jonathan-mezach --extension-id new-relic-dashboard-widgets-private --share-with spicer-testtarget

2016-09-07T07:31:16.5939322Z C:\LR\mms\Services\mms\TaskAgentProvisioner\Tools\agents\1.104.1\tasks\ShareExtension\0.7.3\node_modules\tfx-cli\_build\lib\qfs.js:39

2016-09-07T07:31:16.5959313Z function fileAccess(path, mode = exports.F_OK) {

2016-09-07T07:31:16.5969310Z                                ^

2016-09-07T07:31:16.5969310Z SyntaxError: Unexpected token =

2016-09-07T07:31:16.5969310Z     at exports.runInThisContext (vm.js:53:16)

2016-09-07T07:31:16.5979323Z     at Module._compile (module.js:387:25)

2016-09-07T07:31:16.5989316Z     at Object.Module._extensions..js (module.js:422:10)

2016-09-07T07:31:16.5999330Z     at Module.load (module.js:357:32)

2016-09-07T07:31:16.5999330Z     at Function.Module._load (module.js:314:12)

2016-09-07T07:31:16.5999330Z     at Module.require (module.js:367:17)

2016-09-07T07:31:16.6009334Z     at require (internal/module.js:20:19)

2016-09-07T07:31:16.6009334Z     at Object.<anonymous> (C:\LR\mms\Services\mms\TaskAgentProvisioner\Tools\agents\1.104.1\tasks\ShareExtension\0.7.3\node_modules\tfx-cli\_build\lib\command.js:3:12)

2016-09-07T07:31:16.6009334Z     at Module._compile (module.js:413:34)

2016-09-07T07:31:16.6029314Z     at Object.Module._extensions..js (module.js:422:10)

Any ideas if this is related? It worked yesterday by the way.

T-Hugs · 2016-09-07T10:53:09Z

Interesting, I'm not quite sure what that is at the moment. I will look into it when I get a chance. For now can you revert to the previous version?

jmezach · 2016-09-07T11:11:19Z

Unfortunately I can't do that since I'm using the Build and Release tasks for Extensions. They simply download the latest version of the TFS CLI onto the build agent and I don't currently have a dedicated agent available.

T-Hugs · 2016-09-07T11:13:38Z

Ok. For now I will republish the former version and add a beta tag to the new one. Sorry for the confusion.

T-Hugs · 2016-09-07T11:36:09Z

So, I think this was related to switching to ES6 output, which could have caused issues on older versions of nodejs. I switched back to ES5. Would you mind trying again?

bryanmacfarlane · 2016-09-07T11:38:06Z

node should be packaged with tfx like we did with old node agent ...

jmezach · 2016-09-07T11:42:11Z

Well, the good news is that sharing the extension with another account works again now. Unfortunately installing the extension into an account still fails, although with a different error message than originally reported:

2016-09-07T11:40:09.7905624Z [command]C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\1.104.1\tasks\InstallExtension\0.7.3\node_modules\.bin\tfx.cmd extension install --token ******** --service-url https://marketplace.visualstudio.com/ --publisher jonathan-mezach --extension-id new-relic-dashboard-widgets-private --accounts spicer-testtarget

2016-09-07T11:40:10.7235623Z TFS Cross Platform Command Line Interface v0.3.30

2016-09-07T11:40:10.7245614Z Copyright Microsoft Corporation

2016-09-07T11:40:15.1498123Z Error: Failed Request: Unauthorized(401) -

T-Hugs · 2016-09-07T12:42:23Z

Ok, thanks for the info. I will have to look into this more when I get back in the office on Friday. Installation worked fine for me when I tested with my account, so I'm not sure why you're getting a 401. I will forward this thread to someone else on my team in case they are able to take a look while I'm out.

jmezach · 2016-09-14T07:41:50Z

Any updates on this?

T-Hugs · 2016-09-14T12:59:03Z

Hey Jonathan, I've had a number of people try with the new version of TFX and so far everyone is able to install extensions again. Can you double-check your personal access token? For now, create one that has permissions for "All accessible accounts" and "All scopes". If that works, you should be able to reduce the set of scopes to these:

jmezach · 2016-09-14T13:51:53Z

Ah, it looks like it works again now. I probably didn't have the right scopes checked. Is there any up-to-date documentation on which ones you actually need? It looks like these have changed recently.

T-Hugs · 2016-09-14T13:59:37Z

Good news! I'll make sure the documentation gets updated. Thanks.

bfcamara mentioned this issue Aug 23, 2016

Installing Extensions no longer works microsoft/azure-devops-extension-tasks#8

Closed

T-Hugs mentioned this issue Aug 30, 2016

Better guidance on the appropriate "Service url" to use #144

Open

T-Hugs closed this as completed Sep 7, 2016

bfcamara mentioned this issue Sep 7, 2016

Error when trying to publish an extension microsoft/azure-devops-extension-tasks#11

Closed

T-Hugs reopened this Sep 7, 2016

T-Hugs closed this as completed Sep 14, 2016

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Can not install extensions via commandline #141

Can not install extensions via commandline #141

jhandel commented Aug 19, 2016

T-Hugs commented Aug 19, 2016

jhandel commented Aug 19, 2016

T-Hugs commented Aug 19, 2016

jhandel commented Aug 19, 2016

jdshkolnik commented Aug 22, 2016

brunopssp commented Aug 24, 2016

T-Hugs commented Aug 24, 2016

T-Hugs commented Sep 6, 2016

T-Hugs commented Sep 7, 2016 •

edited

jmezach commented Sep 7, 2016 •

edited

T-Hugs commented Sep 7, 2016

jmezach commented Sep 7, 2016

T-Hugs commented Sep 7, 2016

T-Hugs commented Sep 7, 2016

bryanmacfarlane commented Sep 7, 2016

jmezach commented Sep 7, 2016

T-Hugs commented Sep 7, 2016

jmezach commented Sep 14, 2016

T-Hugs commented Sep 14, 2016 •

edited

jmezach commented Sep 14, 2016

T-Hugs commented Sep 14, 2016

Can not install extensions via commandline #141

Can not install extensions via commandline #141

Comments

jhandel commented Aug 19, 2016

T-Hugs commented Aug 19, 2016

jhandel commented Aug 19, 2016

T-Hugs commented Aug 19, 2016

jhandel commented Aug 19, 2016

jdshkolnik commented Aug 22, 2016

brunopssp commented Aug 24, 2016

T-Hugs commented Aug 24, 2016

T-Hugs commented Sep 6, 2016

T-Hugs commented Sep 7, 2016 • edited

jmezach commented Sep 7, 2016 • edited

T-Hugs commented Sep 7, 2016

jmezach commented Sep 7, 2016

T-Hugs commented Sep 7, 2016

T-Hugs commented Sep 7, 2016

bryanmacfarlane commented Sep 7, 2016

jmezach commented Sep 7, 2016

T-Hugs commented Sep 7, 2016

jmezach commented Sep 14, 2016

T-Hugs commented Sep 14, 2016 • edited

jmezach commented Sep 14, 2016

T-Hugs commented Sep 14, 2016

T-Hugs commented Sep 7, 2016 •

edited

jmezach commented Sep 7, 2016 •

edited

T-Hugs commented Sep 14, 2016 •

edited