delta/gitlab/gitlab-ce.git/lib/api/deploy_keys.rb, branch fe-commit-mr-pipelines gitlab.com: gitlab-org/gitlab-ce.git Merge branch 'grapify-deploy-keys' into 'master' 2017-01-24T12:45:09+00:00 Rémy Coutable remy@rymai.me 2017-01-24T12:45:09+00:00 01fa19edfe2646ad904db6ff50047c2eab61e9d9 Grapify all endpoints of the deploy keys API See merge request !8721 

Grapify all endpoints of the deploy keys API

See merge request !8721
 Merge branch 'fix-users-deleting-public-deployment-keys' into 'security' 2017-01-23T18:41:58+00:00 Robert Speicher robert@gitlab.com 2017-01-19T17:11:48+00:00 60d1dcb83ac97e3d0dfd9cdf0daa970671ba3d68 Fix users being able to delete instance public deployment keys See merge request !2049 

Fix users being able to delete instance public deployment keys

See merge request !2049
 Grapify all endpoints of the deploy keys API 2017-01-23T16:06:57+00:00 Robert Schilling rschilling@student.tugraz.at 2017-01-23T16:06:57+00:00 18417c9ee8b0e0bfa4ee41dd8ada969c0ede07f9 






Use declared_params helper in API
2016-11-14T14:22:06+00:00

Robert Schilling
rschilling@student.tugraz.at

2016-11-14T13:44:27+00:00

76bd09326fe070d4c865b6fbc1718673d096c178












Fixes various errors when adding deploy keys caused by not exiting the control flow.
2016-10-26T10:54:47+00:00

Joshua Welsh
joshua.welsh@performancehorizon.com

2016-10-11T09:02:51+00:00

ce4760bbd57f3b30b0e3845493ed4e39cc463359

When adding a deploy key that already exists in the project the existing key would not be returned, resulting in an attempt to create a new one, which in turn caused a 500 error due to an ActiveRecord exception.

When adding a deploy key that exists within another project the key would be joined to the project, but would also attempt to create a new one, which resulted in a 400 error due to the key already existing.

Fixes #22741
Fixes #21754

Signed-off-by: Rémy Coutable <remy@rymai.me>





When adding a deploy key that already exists in the project the existing key would not be returned, resulting in an attempt to create a new one, which in turn caused a 500 error due to an ActiveRecord exception.

When adding a deploy key that exists within another project the key would be joined to the project, but would also attempt to create a new one, which resulted in a 400 error due to the key already existing.

Fixes #22741
Fixes #21754

Signed-off-by: Rémy Coutable <remy@rymai.me>







Namespace EnableDeployKeyService under Projects
2016-08-08T18:59:51+00:00

Z.J. van de Weg
zegerjan@gitlab.com

2016-08-08T18:32:10+00:00

7e47a82899bdb10d2cdc61ce237a25bfa7f8a392












Create service for enabling deploy keys
2016-08-05T09:38:17+00:00

Z.J. van de Weg
zegerjan@gitlab.com

2016-08-05T09:35:44+00:00

554e18ab025fcd86001faa57fab14fe3ca28a672












Move deploy_key tests to deploy_key_spec.rb
2016-08-04T14:55:20+00:00

Z.J. van de Weg
zegerjan@gitlab.com

2016-08-04T11:09:10+00:00

460065b743a5f28d92bda71b0e778b01cd369d80

Also, fix the failing test in the process





Also, fix the failing test in the process







Use Grape DSL for deploy keys endpoints
2016-08-03T19:04:14+00:00

Z.J. van de Weg
zegerjan@gitlab.com

2016-08-03T14:45:35+00:00

2b6bd6a33f765175222cdb88cd927e420864a236

Also a minor clean up of the post endpoint





Also a minor clean up of the post endpoint







Endpoints to enable and disable deploy keys
2016-08-03T14:00:22+00:00

Z.J. van de Weg
zegerjan@gitlab.com

2016-08-03T12:45:32+00:00

da3d3ba89c19364ca626eb57380e1e33bd344902

Resolves #20123





Resolves #20123