| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
It adds correlation ids wherever possible
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
refactor: remove commandargs.GenericArgs
Closes #212
See merge request gitlab-org/gitlab-shell!506
|
| |
| |
| |
| |
| | |
parse logic will only run if the executable accept args.
healthcheck is the only one not accepting arguments.
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Switch to labkit for logging system setup
Closes #271
See merge request gitlab-org/gitlab-shell!504
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- We start supporting the "color" format for logs.
- We now respond to SIGHUP by reopening the log file.
- We now respect the log format when no log filename is specified.
Output to syslog in the event of logging system setup is preserved in
OpenSSH mode.
Changelog: added
|
|\ \
| |/
|/|
| |
| | |
Modify regex to prevent partial matches
See merge request gitlab-org/security/gitlab-shell!6
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Logrus buffers its output internally, which makes these tests fail
intermittently. They're also not a good example to follow generally.
We now have acceptance tests that exercise this functionality so I'm
pretty relaxed about losing the expectations. However, we can test
them by inspecting the server-received metadata too, so there's no loss
of coverage here.
The move from logrus to labkit for logging also makes these tests hard
to justify keeping.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Update go-proxyproto to v0.6.0
See merge request gitlab-org/gitlab-shell!499
|
| | | |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
Switch to labkit/log for logging functionality
See merge request gitlab-org/gitlab-shell!498
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| | |
A RoundTripper for tracking the duration of an http request
is introduced
|
| |
| |
| |
| | |
already includes it
|
| |
| |
| |
| |
| | |
They are going to be used to determine whether a server is alive
and ready to accept traffic
|
| |
| |
| |
| |
| |
| |
| |
| | |
When interruption signal is sent, we are closing ssh listener to
prevent it from accepting new connections
Then after configured grace period, we cancel the context to
cancel all ongoing operations
|
|\ \
| | |
| | |
| | |
| | | |
Refactor testhelper.PrepareTestRootDir using t.Cleanup
See merge request gitlab-org/gitlab-shell!493
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | | |
Change default logging format to JSON
See merge request gitlab-org/gitlab-shell!476
|
| | | |
|
| | | |
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| | |
Geo SSH proxy push currently impossible when the only
action that happens is branch removal. This fix
works in a way that it waits for flush packet from git
and then checks pkt lines to determine is pack data is expected.
The thing is that git doesnt send pack data when only
branch removal happens. Explanation is in
https://gitlab.com/gitlab-org/gitlab/-/issues/330494
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Gitaly project now properly respects module release flow
and includes a module suffix in the package name. It requires
to re-write all non-suffixed imports with suffixed of a specific
version of tha module. With proper module versioning we don't
need to use a 'replace' directive to point to specific commit
and can use semantic versioning for the gitaly dependency.
Part of: https://gitlab.com/gitlab-org/gitaly/-/issues/3177
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Fix opentracing setup for gitlab-sshd
Closes #501
See merge request gitlab-org/gitlab-shell!473
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, opentracing (if configured) was initialized late in the
gitlab-shell process's lifespan, coming just before making a gRPC
call to Gitaly.
By moving the opentracing initialization to be at process startup, we
make it available for the whole process lifecycle, which is very useful
to gitlab-sshd, as it means we'll only call tracing.Initialize() once
on process startup, rather than once per SSH connection.
To get this working, we need to introduce a context to gitlab-sshd.
This carries the client/service name, but also carries an initial
correlation ID. The main outcome of this is that all calls to the
authorized_keys endpoint from a given gitlab-sshd process will now
share a correlation ID. I don't have a strong opinion about this either
way.
Changelog: fixed
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
Respect parent context for Gitaly calls
See merge request gitlab-org/gitlab-shell!469
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Without these changes, Gitaly calls would not be linked to a parent
context. This means that they would have an unassociated correlationID,
and Gitaly RPC calls would not be cancel()ed by parent context
cancellation.
Changelog: fixed
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This behaviour dates from when Gitaly RPCs were executed in Ruby by a
Go subprocess. It's not needed for gitlab-shell now that it's in Go,
and it's a very strange thing for gitlab-sshd. Best just to remove it.
If we wanted to retain this behaviour, we could have an `os.Chdir` call
in the gitlab-shell binary, but I just don't think it's needed.
Changelog: fixed
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
gitlab-sshd: Respect the ssl_cert_dir config
Closes #516
See merge request gitlab-org/gitlab-shell!467
|
| |/
| |
| |
| | |
Changelog: fixed
|