summaryrefslogtreecommitdiff
path: root/lib/api
diff options
context:
space:
mode:
authorRichard Clamp <richardc@unixbeard.net>2017-05-22 15:49:19 +0100
committerRichard Clamp <richardc@unixbeard.net>2017-05-22 15:49:19 +0100
commitbb8ae56085cbae9545f8a78d0131bb857f53fbf6 (patch)
tree7571659c4b17ce1f89af062d035aab25a457cf12 /lib/api
parenta4407e75d374f65d8638d40eadbd0ec8c32cd6f6 (diff)
downloadgitlab-ce-bb8ae56085cbae9545f8a78d0131bb857f53fbf6.tar.gz
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.
Diffstat (limited to 'lib/api')
-rw-r--r--lib/api/v3/deploy_keys.rb1
1 files changed, 1 insertions, 0 deletions
diff --git a/lib/api/v3/deploy_keys.rb b/lib/api/v3/deploy_keys.rb
index bbb174b6003..b90e2061da3 100644
--- a/lib/api/v3/deploy_keys.rb
+++ b/lib/api/v3/deploy_keys.rb
@@ -41,6 +41,7 @@ module API
params do
requires :key, type: String, desc: 'The new deploy key'
requires :title, type: String, desc: 'The name of the deploy key'
+ optional :can_push, type: Boolean, desc: "Can deploy key push to the project's repository"
end
post ":id/#{path}" do
params[:key].strip!