feat: add organization as an optional parameter in Azure DevOps connection form#7459
Merged
Conversation
…ction creation. Users can now create an Azure DevOps connection using a PAT that is limited to a single organization. This means users are not required to use PATs with access to all their organizations.
…ction creation. Users can now create an Azure DevOps connection using a PAT that is limited to a single organization. This means users are not required to use PATs with access to all their organizations.
The test case was incorrect. When an invalid PAT is provided, the Azure DevOps API redirects the user to the login page. Go's HTTP client automatically follows the redirect when it receives a 302 status code. To circumvent this, I made adjustments to the test case.
klesh
previously approved these changes
May 15, 2024
klesh
approved these changes
May 17, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Users can now create an Azure DevOps connection using a PAT that is limited to a single organization. This means users are not required to use PATs with access to all their organizations. Currently, this feature is only applicable to the Azure DevOps Go plugin. Once confirmed that everything works as intended, it should be moderate effort to also integrate it into the python version and the new onboarding screens.
Does this close any open issues?
Closes #7243
Screenshots
The Azure DevOps Go connection form now includes a new section called
Personal Access Token Scope, where users can choose whether the PAT is scoped or unscoped.All accessible organizationsoption.Other Information
The following endpoints are called to check if the connection is working (test connection button)
GET /_apis/profile/profiles/meGET /<organization>/_apis/projects