Add HTTP proxy policy setting for Template Sync

guides/common/modules/proc_synchronizing-templates-with-an-existing-repository.adoc

@@ -45,7 +45,14 @@ Do not specify a passphrase.
 ----
 # sudo --user foreman ssh _git.example.com_
 ----
-. Configure the Template Sync plugin settings on a *Template Sync* tab.
-.. Change the *Branch* setting to match the target branch on a Git server.
-.. Change the *Repo* setting to match the Git repository.
-For example, for the repository located in `[email protected]/templates.git` set the setting into `[email protected]/templates.git`.
+. In the {ProjectWebUI}, provide details for your Git repository:
+.. Navigate to *Administer > Settings*.
+.. Click the *Template Sync* tab.
+.. Change the *Branch* setting to define the target branch of the repository.
+.. Change the *Repo* setting to define the repository URL.
+.. If you want to use an HTTP proxy to connect to the repository, change the *HTTP proxy policy* setting to `Global default HTTP proxy` or `Custom HTTP proxy`.
+
+.Next steps
+
+* To import templates from your repository, continue with xref:Importing_Templates_{context}[].
+* To export templates to your repository, continue with xref:Exporting_Templates_{context}[].

guides/common/modules/ref_template-sync-settings.adoc

@@ -12,6 +12,7 @@
 Case-insensitive.
 Snippets are not filtered.
 | *Force import* | No | If set to `Yes`, locked templates are overwritten during an import.
+| *HTTP proxy policy* | Global default HTTP proxy | HTTP proxy policy for template sync.
 | *Lock templates* | Keep, do not lock new | How to handle lock for imported templates.
 | *Metadata export mode* | Refresh | Default metadata export mode.