delta/gitlab/gitlab-shell.git/go.sum, branch 491-support-proxy-protocol

gitlab-sshd: Support the PROXY protocol

2021-04-09T11:22:40+00:00

gitlab-sshd: Acceptance test for the discover command

2021-03-17T12:10:46+00:00

With this, we can start to build confidence in making changes to
gitlab-sshd.

Add monitoring endpoint to sshd

2021-02-16T19:38:43+00:00

Add a basic monitoring endpoint to the sshd command.
* Listen on localhost port 9122 by default.
* Integrate build/version info.
* Update example config.

https://gitlab.com/gitlab-org/gitlab-shell/-/issues/121

Signed-off-by: Ben Kochie

Update Go modules

2021-02-11T13:47:32+00:00

Some pre-work for adding Prometheus metrics to SSH server.
* Update Go modules to latest.
* Add Go 1.15 build.

https://gitlab.com/gitlab-org/gitlab-shell/-/issues/121

Signed-off-by: Ben Kochie

RFC: Simple built-in SSH server

2021-01-18T18:36:25+00:00

Update Gitaly module dependency

2020-10-01T14:12:24+00:00

This updates Gitaly's latest Protocol Buffer definitions, which were
last updated in Feburary 2020, with the latest version of Gitaly. This
is done to ensure the definitions are in sync with Workhorse
(https://gitlab.com/gitlab-org/gitlab-workhorse/-/merge_requests/619)
and Gitaly.

Because we started tagging Gitaly versions `v13.x.x` instead of
`v1.x.x`, `go get` refuses to update the Gitaly module using the latest
tag or SHA (https://gitlab.com/gitlab-org/gitaly/-/issues/3177).  Go
tries to enforce semantic compatibility by requiring the use of module
paths (e.g. `m/v13`), and Gitaly doesn't adhere to this scheme.

To workaround this issue, we use the replace directive
(https://github.com/golang/go/wiki/Modules#when-should-i-use-the-replace-directive):

```
go mod edit -replace gitlab.com/gitlab-org/gitaly=gitlab.com/gitlab-org/gitaly@3f5e218def93024f3aafe590c22cd1b29f744105
```

Make it possible to propagate correlation ID across processes

2020-09-21T04:40:40+00:00

Previously, gitlab-shell did not pass a context through the application.
Correlation IDs were generated down the call stack instead of passed
around from the start execution.

This has several potential downsides:

1. It's easier for programming mistakes to be made in future that lead
to multiple correlation IDs being generated for a single request.
2. Correlation IDs cannot be passed in from upstream requests
3. Other advantages of context passing, such as distributed tracing is
not possible.

This commit changes the behavior:

1. Extract the correlation ID from the environment at the start of
the application.
2. If no correlation ID exists, generate a random one.
3. Pass the correlation ID to the GitLabNet API requests.

This change also enables other clients of GitLabNet (e.g. Gitaly) to
pass along the correlation ID in the internal API requests
(https://gitlab.com/gitlab-org/gitaly/-/issues/2725).

Fixes https://gitlab.com/gitlab-org/gitlab-shell/-/issues/474

Set client name when making requests to Gitaly

2020-05-22T05:35:56+00:00

Move go code up one level

2019-10-18T10:47:25+00:00