You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `password` field can either be an actual password (not recommended) or a GitHub token, as described in the {git-sync-docs}[git-sync documentation].
95
96
<8> A map of optional configuration settings that are listed in the {git-sync-docs}[git-sync documentation]. +
96
97
These settings are not verified.
97
-
<9> Multiple repositories can be defined. Only the `repo` field is mandatory.
98
-
<10> Logging can be configured as described in xref:concepts:logging.adoc[].
98
+
<9> Valid `git-config` settings can be passed here N.B. a warning will be triggered if both `http.sslCAInfo` is defined here and the field `caCertSecretName` is specified (as it maps onto the same config setting).
99
+
<10> An optional secret used for holding CA certificates that will be used to verify the git server's TLS certificate by passing it to the git config option `http.sslCAInfo` passed with the gitsync command.
100
+
The secret must have a key named `ca.crt` whose value is the PEM-encoded certificate bundle.
101
+
<11> Multiple repositories can be defined. Only the `repo` field is mandatory.
102
+
<12> Logging can be configured as described in xref:concepts:logging.adoc[].
99
103
As git-sync is a command-line tool, just its output is logged and no fine-grained log configuration is possible.
100
104
All git-sync containers are configured via the one `git-sync` field.
0 commit comments