Propagate client identity to gitaly

See merge request gitlab-org/gitlab-shell!436

Enable Secret Detection in CI

See merge request gitlab-org/gitlab-shell!434

Release v13.13.0

See merge request gitlab-org/gitlab-shell!433

GitLab API Client support for client certificates

See merge request gitlab-org/gitlab-shell!432

Release v13.12.0

See merge request gitlab-org/gitlab-shell!431

Remove rubocop from Ruby test

See merge request gitlab-org/gitlab-shell!430

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Upgrade Bundler from 1.17.2 to 2.1.4

Closes #483

See merge request gitlab-org/gitlab-shell!428

https://gitlab.com/gitlab-org/gitlab-shell/-/merge_requests/426
https://gitlab.com/groups/gitlab-org/-/epics/2380



Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Log Content-Length bytes in API response

See merge request gitlab-org/gitlab-shell!427

This will be useful to measure bandwidth sent in response to an API
request, particularly with measuring the /api/v4/internal/lfs endpoint.

Bump default Ruby version to v2.7.2

See merge request gitlab-org/gitlab-shell!426

Part of https://gitlab.com/groups/gitlab-org/-/epics/2380

Release v13.11.0

See merge request gitlab-org/gitlab-shell!425

Fix incorrect actor used to check permissions for SSH receive-pack

See merge request gitlab-org/gitlab-shell!424

During a SSH receive-pack request (e.g. `git push`), gitlab-shell was
incorrectly using the user returned by the `/internal/allowed` API
endpoint to make an SSHReceivePack RPC call. This caused a number of
problems with deploy keys with write access:

1. Keys that were generated by a blocked user would be denied the
ability to write.

2. Keys that were generated by user that did not have write access to
the project would also be denied.

GitLab 12.4 removed the Ruby implementation of gitlab-shell in favor of
the Golang implementation, and these implementations worked slightly
differently. In
https://gitlab.com/gitlab-org/gitlab-shell/blob/v10.1.0/lib/gitlab_shell.rb,
the Ruby implementation would always use `@who` (e.g. `key-123`), but in
gitlab-shell v10.2.0 the Go implementation would always use the user
from the API response.

Reads did not have this issue because the user/deploy key is never
passed to Gitaly for additional permission checks. Writes need this
information for the pre-receive to check access to protected branches,
push rules, etc.

Relates to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/479

Set SSL_CERT_DIR env var when building command

See merge request gitlab-org/gitlab-shell!423

Release v13.10.0

See merge request gitlab-org/gitlab-shell!422

Add support for -version argument

See merge request gitlab-org/gitlab-shell!421

This will help determine the version of the binary particularly on Cloud
Native GitLab, where VERSION may not be shipped with the binaries.

Release v13.9.0

See merge request gitlab-org/gitlab-shell!420

tests: Remove testify assert in favour of require

See merge request gitlab-org/gitlab-shell!419

client: Allow User-Agent header to be overridden

See merge request gitlab-org/gitlab-shell!418

Testify features sub packages `assert` and `require`. The difference is
subtle, and lost on novice Golang developers that don't read the docs.
To create a more consistent code base `assert` will no longer be used.

This change was generated by a running a sed command on all `_test.go`
files, followed by `goimports -w`.