Add support to uninstall an extension

[gereon77]

Right now I miss the possibility to uninstall an extension from the server. This might become handy during extension development when you want to test update extension and install extension. Or if for some reason the extension id has changed and you want to uninstall the old one. Right now I have a work around with a pure REST which does the trick but I would love to see this supported by this great extension.

Thank you in advance. :)

[jessehouwing]

There is no option in tfx-cli to uninstall extensions.

This would first have to be implemented in tfx-cli, I don't want to take additional REST API dependenies in this extension, those are almost all abstarcted away behind tfx-cli.

[jessehouwing]

You're free to request this feature in tfx-cli.

[gereon77]

Thank you Jesse. I opened an issue in the tfx cli repo.

[gereon77]

Hi again... It's available with the newest cli now: microsoft/tfs-cli#316 ... So may I count on an update of this extension? :)

[jessehouwing]

Pull requests welcome ;). If none comes in I'll see when I can build it. Should also be pretty straightforward, but this is built by volunteers :)

…

On Thu, 2 May 2019, 09:07 gereon77, ***@***.***> wrote: Hi again... It's available with the newest cli now: microsoft/tfs-cli#316 <microsoft/tfs-cli#316> ... So may I count on an update of this extension? :) — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#134 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA724S2JJQDPL5EJVBJB4KDPTKHMNANCNFSM4HJKDKQQ> .

[jessehouwing]

Is unpublish really what you were after?

Or uninstall from account? Cause it looks like you got the first..

[praneetloke]

I came here wanting an "uninstall" action from an organization, not an unpublish from the marketplace. Looking at the changes in the tfx-cli I do think it removes the extension from the marketplace and not from an organization.

[jessehouwing]

That's what I thought.

…

On Thu, Nov 14, 2019 at 7:32 PM Praneet Loke ***@***.***> wrote: I came here wanting an "uninstall" action from an organization, not an unpublish from the marketplace. Looking at the changes <microsoft/tfs-cli@2810463#diff-0047de3cc939020920314067c4be8fe2R10> in the tfx-cli I do think it removes the extension from the marketplace and not from an organization. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#134?email_source=notifications&email_token=AA724S63FZRHZMNPKWBUSC3QTWKSDA5CNFSM4HJKDKQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEC2RXI#issuecomment-554019037>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA724SZ5LV23IGHRPVGGSV3QTWKSDANCNFSM4HJKDKQQ> .

[praneetloke]

Having said that, exposing the "unpublish" action would be good. For my workflow, I am publishing a private VSIX, test the private one, and unpublish it from the marketplace if everything was successful. I can open a new issue if you'd like, @jessehouwing ?

[jessehouwing]

@praneetloke I'll take pull requests on this one, should be relatively simple, it can take the IsValidExtension or QueryVersion as a baseline,

Personally I just leave the private extension out there.

[praneetloke]

@jessehouwing since writing the above comment, I have changed my workflow also to leave the test extension published and shared privately with my test organization. I still see a value in having the ability to uninstall an extension, though.

[jessehouwing]

Unpublish is now exposed.
Uninstall is still not an available part of tfx-cli.