delta/gitlab/gitlab-shell.git/internal/gitlabnet, branch patch-2 gitlab.com: gitlab-org/gitlab-shell.git Generate and log correlation IDs 2020-07-31T12:58:42+00:00 Stan Hu stanhu@gmail.com 2020-07-31T12:58:42+00:00 87402ed127d9855b8123e5e08a4c89d373cc79e8 This will make it easier to tie an SSH access request to Rails API and Gitaly requests. 
This will make it easier to tie an SSH access request to Rails API and
Gitaly requests.
Log SSH key details 2020-07-23T06:19:57+00:00 Stan Hu stanhu@gmail.com 2020-07-23T06:19:57+00:00 6555cb81641af139aa65865c4a749a8c7d53e07e Right now when a client such as gitlab-shell calls the `/api/v4/internal/allowed` API, the response only tells the client what user has been granted access, and it's impossible to tell which deploy key/token was used in the authentication request. This commit adds logs for the following when available: 1. `gl_key_type` (e.g. `deploy_key` or `key`) 2. `gl_key_id` These fields make it possible for admins to identify the exact record that was used to authenticate the user. API changes in the `/internal/allowed` endpoint in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/37289 are needed to support this. Relates to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/203 
Right now when a client such as gitlab-shell calls the
`/api/v4/internal/allowed` API, the response only tells the client what
user has been granted access, and it's impossible to tell which deploy
key/token was used in the authentication request.

This commit adds logs for the following when available:

1. `gl_key_type` (e.g. `deploy_key` or `key`)
2. `gl_key_id`

These fields make it possible for admins to identify the exact record
that was used to authenticate the user.

API changes in the `/internal/allowed` endpoint in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/37289 are needed
to support this.

Relates to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/203
Ensure we are passing the parsed secret 2020-05-06T20:57:01+00:00 DJ Mountney dj@gitlab.com 2020-05-06T20:57:01+00:00 e6482b8797cc34a024429f5ce9e75e11a139fd3b Rather than the secret file. The parsing of the file was already done in the gitlab-shell config. This fixes an issue where a recent refactor of the gitlabnet client passed the wrong value. 
Rather than the secret file. The parsing of the file was already done in
the gitlab-shell config.

This fixes an issue where a recent refactor of the gitlabnet client
passed the wrong value.
Move gitlabnet client to client package 2020-05-04T21:19:47+00:00 John Cai jcai@gitlab.com 2020-05-04T17:59:49+00:00 91f45342c4ff29a24c61812d539ac745dbb1570a 






Geo Pull custom action support
2020-04-17T06:23:33+00:00

Ash McKenzie
amckenzie@gitlab.com

2020-04-17T06:23:12+00:00

4f4acf4a1e523678355b06234016fa632bae282e












Allow allowedPayloadPath to be provided
2020-04-17T06:23:33+00:00

Ash McKenzie
amckenzie@gitlab.com

2020-04-03T05:28:35+00:00

2cb9461f0b188a18ff219cb1b5f12cb6b18a954b












Rename Geo Push custom action test
2020-04-17T06:23:33+00:00

Ash McKenzie
amckenzie@gitlab.com

2020-04-03T05:27:46+00:00

95f34305e0701bc74e949e4b9b9a5b6ac44ecbb1












Rename action to be more accurate
2020-04-17T06:23:33+00:00

Ash McKenzie
amckenzie@gitlab.com

2020-04-03T05:26:50+00:00

8e5c72d7700cc0aebac9475144a9d30e97951ef0












Rename allowed payload JSON for accuracy
2020-04-17T06:23:33+00:00

Ash McKenzie
amckenzie@gitlab.com

2020-04-03T05:22:53+00:00

76f528fbd3c87434e7ca9873f1840682eee72095












Log internal HTTP requests
2020-03-11T04:58:15+00:00

Stan Hu
stanhu@gmail.com

2020-03-07T08:46:26+00:00

70c1b494b81f0035b71e47a65a70a8b86a2c8427

This restores the previous behavior of logging the success and failures
of internal HTTP requests.

Part of https://gitlab.com/gitlab-org/gitlab/issues/207916





This restores the previous behavior of logging the success and failures
of internal HTTP requests.

Part of https://gitlab.com/gitlab-org/gitlab/issues/207916