-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug][Blueprints] 400 error when adding Azure DevOps scope to existing project #7504
Comments
To resolve the 400 error when adding an Azure DevOps scope to an existing project with a GitHub connection, you need to ensure that the scope details and connection information are correctly mapped and validated. The error message indicates that the argument list is too long, which suggests that the payload size might be an issue. Here are some steps to address this:
By implementing these changes, you should be able to resolve the 400 error and successfully add Azure DevOps scopes to an existing project with a GitHub connection [1][2].
|
Would you like to try the |
Will do! What's the difference between the two? |
Well, the one without |
@klesh somehow the repos I can see in the python plugin are not showing up in the go plugin. |
Oh, I see. What is the different between those repos? loop @mr-ks |
@slaterx, the two plugins use different database tables, did you manage to successfully create the connection in the go plugin? One important distinction is that the Go version excludes disabled repositories. Is this possibly why you're not seeing some repositories? incubator-devlake/backend/plugins/azuredevops_go/api/remote_helper.go Lines 150 to 155 in 288c01e
|
@mr-ks thank you for explaining the distinction, indeed the difference comes from the disabled repos showing up on the python plugin. In Azure DevOps land, a disabled repo means that only the source code is unavailable. Pipelines, boards and other items might still be available and actively used by teams (which is our case). |
I think we should allow disabled repos because the use case sounds reasonable. |
Search before asking
What happened
On a project with an existing github connection (such as #7503), adding an Azure DevOps connection to it gives a 400 error in the UI:
Inside lake microservice container, the error is the below:
What do you expect to happen
AzureDevops scopes are added to existing project.
How to reproduce
Anything else
Same environment where #7503 is happening.
Version
1.0.0-beta6
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: