I'm using the API to automate creation of a project. As follows:
returnstatus=`curl -sL -w "%{http_code}" -o $tmpfile --header
"PRIVATE-TOKEN: $gitlabaccesstoken" \
--data "name=$sitename" \
--data "namespace_id=$namespaceid" \
--data "visibility_level=0" \
https://myserver/api/v3/projects`
If this command succeeds, it should return status code 201, and json into
$tmpfile. Unfortunately, it's returning 404, and the generic 404 html into
$tmpfile. ... But ... The project was actually created successfully. It has the
right name, it's in the right namespace (group), and its visibility is set
correctly. The only thing that's incorrect is the http status code, and html
response.
The gitlabaccesstoken belongs to user "root" who is not a member of the group
where the new project was created. So I thought maybe behind the scenes, root
is granted access to create the project, but for some reason is not granted
access to read it back, generating the json response? Or maybe there's a race
condition in the server, where it's trying to generate the json quicker than
the project is fully ready? Or some other bug?
Can I look in some logs somewhere to determine why it's failing to return
correctly?
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/gitlabhq/BY1PR0401MB12558F1C92EAC1B8DD48CCF1DC4A0%40BY1PR0401MB1255.namprd04.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
