summaryrefslogtreecommitdiff
path: root/internal/testhelper/testdata/testroot
Commit message (Collapse)AuthorAgeFilesLines
* Acceptance test for Geo pushIgor Drozdov2023-03-171-0/+29
| | | | | It imitates a push to the secondary and verifies that the push is redirected to the primary
* Configure Gitaly storage acceptance testsPatrick Cyiza2023-03-151-1/+1
|
* Perform HTTP request to primary on Geo pushIgor Drozdov2023-03-031-0/+2
| | | | | | | | | Currently, we perform a request to Gitlab Rails that proxies the request to primary However, it causes timeouts on big pushes and consumes large amount of memory. We can perform an HTTP request directly from Gitlab Shell instead and stream the response to the user
* Fix broken Gitaly integration testsPatrick Bajao2022-11-231-2/+2
| | | | | | | | | | | Gitaly started to require `Repository` information for certain commands like upload-pack, upload-archive, and receive-pack. However, gitlab-shell tests are sending `git_object_directory` and `git_alternate_object_directories` that do not exist. To fix the tests, we set those to an existing directory in the created repository.
* gitlab-sshd: Add support for configuring host certificatesStan Hu2022-06-268-0/+82
| | | | | | | | | | | | | | | | | This adds support for specifying host certificates via the `host_cert_files` option and advertises the signed key to the client. This acts similarly to OpenSSH's `HostCertificate` parameter: gitlab-sshd attempts to match a host key to its certificate, and then substitutes the matching host key with a certificate signed by a trusted certificate authority's key. This is the first requirement to supporting SSH certificates. This will enable the client to trust the server if both trust a common certificate authority. The `TrustedUserCAKeys` option will need to be supported later for the server to trust all user keys signed by this certificate authority. Relates to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/495
* Make ProxyHeaderTimeout configurableIgor Drozdov2022-05-191-0/+1
| | | | | | | | Issue: https://gitlab.com/gitlab-org/gitlab-shell/-/issues/576 ProxyHeaderTimeout must be small to avoid DoS risk Let's make the value configurable and 500ms by default
* Allow specifying formatted durations in configIgor Drozdov2022-05-191-0/+3
| | | | | - If an integer is specified, we assume that these are seconds - A duration of format "500ms", "10s", "1m", etc... accepted
* Always use Gitaly sidechannel connectionsJacob Vosmaer2022-05-021-23/+0
| | | | | | | Before this change, the GitLab internal API could use a boolean response field to indicate whether gitlab-shell should make sidechannel connections go Gitaly. We now ignore that response field and always use sidechannel connections.
* Support parsing `use_sidechannel` API response fieldJacob Vosmaer2022-01-251-0/+23
| | | | | | This field will act as a feature flag that controls whether gitlab-shell uses the old SSHUploadPack RPC or the new SSHUploadPackWithSidechannel.
* Sshd: Log same correlation_id on auth keysIgor Drozdov2021-07-271-0/+1
|
* Add a simple acceptance test for git-receive-packSean McGivern2021-05-201-3/+3
|
* Add acceptance test for git-lfs-authenticateSean McGivern2021-05-171-0/+22
|
* GitLab API Client support for client certificatesPaul Okstad2020-11-172-0/+86
|
* Geo Pull custom action supportAsh McKenzie2020-04-171-0/+40
|
* Rename allowed payload JSON for accuracyAsh McKenzie2020-04-171-1/+1
|
* Remove support for Custom data.info_message210-remove-action-custom-inform_client-once-12-3-has-been-releasedAsh McKenzie2019-12-241-2/+1
|
* Move go code up one levelNick Thomas2019-10-1810-0/+114
View Lorry Controller Status