diff options
| author | Pavlo Strokov <pstrokov@gitlab.com> | 2020-09-08 13:07:22 +0300 |
|---|---|---|
| committer | Zeger-Jan van de Weg <git@zjvandeweg.nl> | 2020-09-08 13:07:22 +0300 |
| commit | d87f0757c880a28b20338fd9533495688eeece95 (patch) | |
| tree | 35f26f53712adee29f8c92c36a57e00c0b249bcc /go.mod | |
| parent | 785bebf7fb05c6c4457c75c011a01b1bede3f3a9 (diff) | |
Pass correlation_id over to gitaly-ssh
When gitaly-ssh is called it doesn't receive correlation_id.
That is why it is hard to understand what to what chain of calls
this call is related.
correlation_id passed as env var 'CORRELATION_ID' to gitaly-ssh
process. So it would be picked by it and used in outgoing requests.
In order to cover other missing parts where correlation_id should
be passed the client.DialContext method includes interceptors for it
by default. If correlation_id is present in the context.Context used
to invoke the method it will be passed to the remote.
Part of: https://gitlab.com/gitlab-org/gitaly/-/issues/3047
Diffstat (limited to 'go.mod')
| -rw-r--r-- | go.mod | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -13,11 +13,13 @@ require ( github.com/lib/pq v1.2.0 github.com/libgit2/git2go/v30 v30.0.5 github.com/olekukonko/tablewriter v0.0.2 + github.com/opentracing/opentracing-go v1.0.2 github.com/prometheus/client_golang v1.0.0 github.com/prometheus/procfs v0.0.3 // indirect github.com/rubenv/sql-migrate v0.0.0-20191213152630-06338513c237 github.com/sirupsen/logrus v1.4.2 github.com/stretchr/testify v1.4.0 + github.com/uber/jaeger-client-go v2.15.0+incompatible gitlab.com/gitlab-org/gitlab-shell v0.0.0-20200821152636-82ec8144fb2a gitlab.com/gitlab-org/labkit v0.0.0-20200507062444-0149780c759d golang.org/x/sync v0.0.0-20190911185100-cd5d95a43a6e |