tfx extension install fails if already installed
See original GitHub issueI’m trying to publish an extension to other extension environments, in tfs build/release.
tfx extension install --vsix (vsix) --service-url (serviceUrl) --pat (pat)
error: Error: Failed Request: Conflict(409) - TF1590010: Extension (extension name) is already installed in this account.
Does this need to be an error? Couldn’t it be a warning instead? If it’s already installed, that’s good.
I guess I need to wrap or catch this somehow so my build doesn’t fail.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Azure Devops Extension Installation - Visual Studio Feedback
We are currently trying to install an publish and install the extension from Azure devops pipeline using the build and release tasks ,...
Read more >TFX-CLI fails on "tfx extension create" - Stack Overflow
According to your error message: error: One or more 'categories' must be provided. You need to add categories to your vss-extension.json ...
Read more >Extension Manifest Reference - Azure DevOps | Microsoft Learn
Start by creating a file named vss-extension.json at the root of your extension folder. This file contains required attributes, like the ...
Read more >tfx-cli - npm
Start using tfx-cli in your project by running `npm i tfx-cli`. There is 1 other project in the npm registry using tfx-cli.
Read more >Security state of the Azure DevOps Marketplace - Scrum Bug
My first problem was to get all the data required to analyze the extensions. Unlike the GitHub Actions Marketplace, where every action is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, I fixed this in 0.7.1 but forgot to close out the issue.
I’ve seen the same problem. Would be nice to have a force switch with the tfx extension install or a uninstall command. Only fix I’ve found was to manually uninstall the extension, which is less than ideal.