We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When project is on a sub-subgroup the key deployment not working. i think the second / is not htmlized revelant part of :
opening connection to <my_gitlab_server>:443... opened starting SSL for <my_gitlab_server>:443... SSL established <- "GET /api/v3/projects/infra-projects%2Fhubapplicatif/web 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: <my_private_token>\r\nConnection: close\r\nHost: <my_gitlab_server>\r\n\r\n" -> "HTTP/1.1 404 Not Found\r\n" -> "Server: nginx\r\n" -> "Date: Wed, 20 Sep 2017 12:38:53 GMT\r\n" -> "Content-Type: application/json\r\n" -> "Content-Length: 25\r\n" -> "Connection: close\r\n" -> "Cache-Control: no-cache\r\n" -> "Vary: Origin\r\n" -> "X-Request-Id: b540fa1c-afcf-4b0b-ab95-be856e807bef\r\n" -> "X-Runtime: 0.015513\r\n" -> "\r\n" reading 25 bytes... -> "{\"error\":\"404 Not Found\"}" read 25 bytes Conn close
in /api/v3/projects/infra-projects %2F hubapplicatif / web the second / between hubapplicatif and web must be %2F
The text was updated successfully, but these errors were encountered:
replace / by %2F in project stored on sub-sub-group
da97c80
url for project in sub sub group are not well formated. replace / by %2F over all the urn resolve issue abrader#39
No branches or pull requests
When project is on a sub-subgroup the key deployment not working.
i think the second / is not htmlized
revelant part of :
puppet agent -t -d
in /api/v3/projects/infra-projects %2F hubapplicatif / web the second / between hubapplicatif and web must be %2F
The text was updated successfully, but these errors were encountered: