Skip to content
Snippets Groups Projects
user avatar
Will Chandler authored
Originally Gitaly would shell out to Gitlab-Shell to make internal API
calls. This had no retained state regarding the secret token, so no
service restarts were required in this scenario.

However, for several years the main Gitaly process has been responsible
for calling the internal API. This will only read the Gitlab-Shell
secret file during its startup process, and subsequent changes to that
will not be detected by Gitaly, leading to spurious 401 errors.

To resolve this, restart the Gitaly service when updating
`gitlab_shell['secret_token']`.

Changelog: fixed
05c84427
History
Name Last commit Last update