Douwe Maan
536a47b4b7
Merge branch 'sh-migrate-can-push-to-deploy-keys-projects-10-3' into 'security-10-3'
...
[10.3] Migrate `can_push` column from `keys` to `deploy_keys_project`
See merge request gitlab/gitlabhq!2276
(cherry picked from commit f6ca52d31bac350a23938e0aebf717c767b4710c)
1f2bd3c0 Backport to 10.3
2018-01-16 17:04:51 -08:00
Richard Clamp
bb8ae56085
Add missing can_push parameter to POST /v3/deploy_keys
...
The v3 API documentation claims that `can_push` is supported when
adding a deploy_key.
https://gitlab.com/gitlab-org/gitlab-ce/blob/8-16-stable/doc/api/deploy_keys.md#add-deploy-key
Here we make good on this promise by adding `can_push` as an optional
parameter so grape can route it.
This was copied from the v4 API.
2017-05-22 15:49:19 +01:00
Rémy Coutable
63360adeae
Add requirements: { id: %r{[^/]+} } for all projects and groups namespaced API routes
...
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-03-16 18:00:24 +01:00
Robert Schilling
67f5522d2e
Remove /projects/:id/keys/.. endpoints
2017-02-07 14:14:15 +01:00
