| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Only validate SSL cert file exists if a value is supplied | Stan Hu | 2021-09-23 | 1 | -4/+18 |
| | | | | | | | | | | This fixes a regression in https://gitlab.com/gitlab-org/gitlab-shell/-/merge_requests/508. If an HTTPS internal API URL were used, gitlab-shell would not work at all. We now handle blank `caFile` properly. Relates to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/529 | ||||
| * | refactor: move away from ioutil (deprecated) | feistel | 2021-08-19 | 1 | -3/+2 |
| | | |||||
| * | test: move os.stat check before the hcc creation | Ash McKenzie | 2021-08-17 | 1 | -7/+7 |
| | | |||||
| * | fix: make sure ErrCafileNotFound is returned only when the file doesn't exist | feistel | 2021-08-11 | 1 | -1/+4 |
| | | |||||
| * | fix: validate client cert paths exist on disk before proceeding | feistel | 2021-08-11 | 1 | -9/+19 |
| | | |||||
| * | Fix formatting via make fmt | Stan Hu | 2021-07-26 | 1 | -1/+1 |
| | | |||||
| * | Switch to labkit/log for logging functionality | Igor Drozdov | 2021-07-22 | 1 | -1/+1 |
| | | |||||
| * | Add tracing instrumentation to http client | Igor | 2021-07-20 | 1 | -1/+2 |
| | | |||||
| * | Update httpclient.go with TLS 1.2 as minimum version | Vitor Meireles De Sousa | 2020-11-17 | 1 | -0/+1 |
| | | |||||
| * | GitLab API Client support for client certificates | Paul Okstad | 2020-11-17 | 1 | -14/+67 |
| | | |||||
| * | Fix gitlab-shell not handling relative URLs over UNIX socketssh-fix-unix-relative-url-access | Stan Hu | 2020-08-20 | 1 | -5/+11 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/4498#note_397401883, if you specify a relative path such as: ``` external_url 'http://gitlab.example.com/gitlab' ``` gitlab-shell doesn't have a way to pass the `/gitlab` to the host. For example, let's say we have: ``` gitlab_url: "http+unix://%2Fvar%2Fopt%2Fgitlab%2Fgitlab-workhorse%2Fsocket" ``` If we have `/gitlab` as the relative path, how do we specify what is the UNIX socket path and what is the relative path? If we specify: ``` gitlab_url: "http+unix:///var/opt/gitlab/gitlab-workhorse.socket/gitlab ``` This is ambiguous. Is the socket in `/var/opt/gitlab/gitlab-workhorse.socket/gitlab` or in `/var/opt/gitlab/gitlab-workhorse.socket`? To fix this, this merge request adds an optional `gitlab_relative_url_root` config parameter: ``` gitlab_url: "http+unix://%2Fvar%2Fopt%2Fgitlab%2Fgitlab-workhorse%2Fsocket" gitlab_relative_url_root: /gitlab ``` This is only used with UNIX domain sockets to disambiguate the socket and base URL path. If `gitlab_url` uses `http://` or `https://`, then `gitlab_relative_url_root` is ignored. Relates to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/476 | ||||
| * | Generate and log correlation IDs | Stan Hu | 2020-07-31 | 1 | -1/+4 |
| | | | | | | This will make it easier to tie an SSH access request to Rails API and Gitaly requests. | ||||
| * | Move gitlabnet client to client packagejc-refactor-gitlabnet-client | John Cai | 2020-05-04 | 1 | -0/+113 |
 |
index : delta/gitlab/gitlab-shell.git | |
| gitlab.com: gitlab-org/gitlab-shell.git |
| summaryrefslogtreecommitdiff |