-
Notifications
You must be signed in to change notification settings - Fork 32
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
Gitlab API v3 is no longer supported #43
Comments
Noticed this as well, after the upgrade to 11.0.0 then 11.0.1 I realised things were borked :( |
I believe #44 that I just submitted will resolve the issue. |
hi, we're getting the exact same message here, using GitLab CE 11.0.2 |
It also doesn't look like the keys endpoint is available anymore in v4: <- "GET /api/v4/projects/38/keys HTTP/1.1\r\nAccept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3\r\nAccept: /\r\nUser-Agent: Ruby\r\nContent-Type: application/json\r\nPrivate-Token: <token_removed>\r\nConnection: close\r\nHost: gitlab.server.com\r\n\r\n" Found the transition doc here: ETA: I tested against a fork of the PR after adding the updated endpoints, and it worked. |
Clearly I have work to do which I want to just wrap up in a v4 support release that maintains v3 compatibility. |
Any update on this? |
OS: Centos 7.5.1804
Module version: v1.0.3
Puppet: v5.5.1
Gitlab: gitlab-ee-11.0.0-ee.0.el7.x86_64
Debug output from failed puppet run.
The text was updated successfully, but these errors were encountered: