Implement ability to update deploy keys (!10383) · Merge Requests · GitLab.org / GitLab FOSS

Implement ability to update deploy keys

What does this MR do?

Implement ability to update deploy keys

Are there points in the code the reviewer needs to double check?

I suppose so if deploy_key added via admin panel, user should not have ability to rename it (because it will be affected to all users) and Edit button not available for public keys (but admins can rename them via admin panel).

And I didn't update documentation.

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

Changelog entry added, if necessary
[ ]~~ Documentation created/updated~~
API support added
Tests
- Added for this feature/bug
- All builds are passing
Conform by the merge request performance guides
Conform by the style guides
Branch has no merge conflicts with master (if it does - rebase it please)
Squashed related commits together

What are the relevant issue numbers?

Closes #3191 (closed)

## What does this MR do?

Implement ability to update deploy keys

## Are there points in the code the reviewer needs to double check?

I suppose so if deploy_key added via admin panel, user should not have ability to rename it (because it will be affected to all users) and `Edit` button not available for `public` keys (but admins can rename them via admin panel).

And I didn't update documentation.

## Screenshots (if relevant)
![screen1](https://cl.ly/3h1b2Z0e0B1J/Image%202017-03-31%20at%2018.13.25.png)
![screen2](https://cl.ly/1Y2C1N2k1c1u/Image%202017-03-31%20at%2018.14.12.png)

## Does this MR meet the acceptance criteria?

- [x] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [ ]~~ [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)~~
- [x] API support added
- Tests
  - [x] Added for this feature/bug
  - [x] All builds are passing
- [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

## What are the relevant issue numbers?

Closes #3191

Implement ability to update deploy keys

What does this MR do?

Are there points in the code the reviewer needs to double check?

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Check out, review, and merge locally

Revert this merge request

Cherry-pick this merge request