Make it possible to propagate correlation ID across processessh-extract-context-from-env

Previously, gitlab-shell did not pass a context through the application.
Correlation IDs were generated down the call stack, since we don't pass
the context around from the start execution.

This has several potential downsides:

1. It's easier for programming mistakes to be made in future which 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

1 files changed, 1 insertions, 1 deletions

diff --git a/internal/config/config.go b/internal/config/config.go
index e7abd59..79c2a36 100644
--- a/internal/config/config.go
+++ b/internal/config/config.go
@@ -37,7 +37,7 @@ type Config struct {
 	Secret                string             `yaml:"secret"`
 	SslCertDir            string             `yaml:"ssl_cert_dir"`
 	HttpSettings          HttpSettingsConfig `yaml:"http_settings"`
-	HttpClient            *client.HttpClient
+	HttpClient            *client.HttpClient `-`
 }
 
 func (c *Config) GetHttpClient() *client.HttpClient {