-
Notifications
You must be signed in to change notification settings - Fork 46
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
Support for GitLab api v4 #57
Comments
Hi @dev-rowbot, I've hit this issue as well. Any luck working around it? We are using node-red-contrib-gitlab and it uses this package to integrate GitLab into NodeRed. Currently, I'm looking for alternatives. |
@smorrisfv unfortunately I was I not able to use this package and ending up writing my own gitlab api module. I only needed a small subset of the API though so I just used requests and called the endpoints directly. |
@dev-rowbot Is your module available anywhere? In the in term, I ended up creating some simple subflows that wrap HTTP requests that act the same as the models provided in this package. They will work for now until I have time to work out a more permanent solution. |
@smorrisfv sorry but its not available anywhere. It's not the entire API so I didn't think it would be of much use to anyone :-) |
From GitLab 11 support for v3 API has been removed - https://docs.gitlab.com/ee/api/v3_to_v4.html
I hit this issue when attempting to use
client.projects.search()
, this fails because searching projects has changed:GET /projects/:search
(use:GET /projects?search=x
)The text was updated successfully, but these errors were encountered: