docs: Add git proxy support docs

Signed-off-by: Sunny <darkowlzz@protonmail.com>
This commit is contained in:
Sunny 2022-01-20 00:36:06 +05:30
parent c99d0039d2
commit 017207d99e
No known key found for this signature in database
GPG Key ID: 9F3D25DDFF7FA3CF
1 changed files with 18 additions and 3 deletions

View File

@ -207,9 +207,9 @@ To be able to support Azure DevOps a compromise solution was built, giving the u
option to select the git library while accepting the drawbacks.
| Git Implementation | Shallow Clones | Git Submodules | V2 Protocol Support |
|---|---|---|---|
| 'go-git' | true | true | false |
| 'libgit2' | false | false | true |
| --- | --- | --- | --- |
| 'go-git' | true | true | false |
| 'libgit2' | false | false | true |
Pull the master branch from a repository in Azure DevOps.
@ -225,6 +225,21 @@ spec:
gitImplementation: libgit2
```
## Git Proxy
A Git proxy can be configured by setting the appropriate environment variables
for proxy configurations, for example `HTTPS_PROXY`, `NO_PROXY`, etc., in the
source-controller pod. There may be some limitations in the proxy support based
on the Git implementations.
| Git Implementation | HTTP_PROXY | HTTPS_PROXY | NO_PROXY | Self-signed Certs |
| --- | --- | --- | --- | --- |
| 'go-git' | true | true | true | false |
| 'libgit2' | false | true | false | true |
**NOTE:** libgit2 v1.2.0 supports `NO_PROXY`, but source-controller uses
libgit2 v1.1.1 at the moment.
## Spec examples
### Checkout strategies