[Darc] Support multiple Azure DevOps PATs
See original GitHub issue- This issue is blocking
- This issue is causing unreasonable pain
Some Azure DevOps accounts cannot create PATs that work across multiple orgs in DevOps. When running darc update-dependencies
in a repo that has dependencies from multiple orgs, darc will throw a 401 unauthorized error because you can’t authenticate for multiple orgs with one PAT.
cc @crummel
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Use personal access tokens - Azure DevOps
Learn how to create and manage personal access tokens (PATs) as alternate passwords to authenticate to Azure DevOps.
Read more >Manage personal access tokens using API - Azure DevOps
Learn how to use the PAT lifecycle management API to get, create, update, and revoke their personal access tokens (PATs).
Read more >Use policies to manage personal access tokens for users
You can limit the creation, scope, and lifespan of new or renewed personal access tokens (PATs) for users in Azure DevOps by enabling...
Read more >Introducing Service Principal and Managed Identity support ...
We are proud to announce that Service Principals and Managed Identities can now be used to authenticate with Azure DevOps.
Read more >New policies for personal access tokens
Personal access tokens (PATs) make it easy to authenticate against Azure DevOps to integrate with your tools and services.
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
The interactive mode can actually work on linux. The “device code” mode works anywhere a console prompt works.
The PAT tool has been merged. I’m going to close this as that should be the preferred way to create PATs for multiple orgs, and it’s just not feasible for us to plumb multiple per org PATs everywhere where it would be needed.