Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-27349

Add support for using a http proxy when syncing templates

XMLWordPrintable

    • Add support for using a http proxy when syncing templates
    • Done
    • SAT-19573Full support for IPV6
    • SAT-19573 - Full support for IPV6
    • False
    • Feature
    • Hide
      .The Template Sync plugin supports using an HTTP proxy to connect to a repository

      You can now use an HTTP proxy to synchronize templates between your Satellite server and a git repository. Configuring an HTTP proxy for template synchronization ensures that Satellite routes the Template Sync request to the repository through the specified proxy server.

      For more information, see link:https://docs.redhat.com/en/documentation/red_hat_satellite/6.17/html-single/administering_red_hat_satellite/index#Synchronizing_Templates_Repositories_admin[Synchronizing template repositories] in _Administering Red Hat Satellite_.
      Show
      .The Template Sync plugin supports using an HTTP proxy to connect to a repository You can now use an HTTP proxy to synchronize templates between your Satellite server and a git repository. Configuring an HTTP proxy for template synchronization ensures that Satellite routes the Template Sync request to the repository through the specified proxy server. For more information, see link: https://docs.redhat.com/en/documentation/red_hat_satellite/6.17/html-single/administering_red_hat_satellite/index#Synchronizing_Templates_Repositories_admin [Synchronizing template repositories] in _Administering Red Hat Satellite_.
    • Done

      Goal:

      • Syncing templates from git should use a HTTP proxy when a default HTTP proxy is set in settings to allow Satellites running in IPV6-only environments to sync templates from IPV4-only accessible git servers

      Acceptance Criteria:{}

      • Template import and export are able to use a HTTP proxy.

      Open questions:

      • Q: the state of http proxies in automation is unknown
        A: ???
      • Q: docs side of things
        A: rn, no change to the actual template syncing procedure
      • Q: hammer?
        A: yes. Changes to api and hammer should automatically propagate to the relevant guides, we'd like to avoid explicitly adding a single step procedure to the product guides
      • Q: permissions?
        A: always should the one from settings, the ones from infrastructure > http proxies only subject to permissions, might have docs impact

              rhn-support-alazik Adam Lazik
              aruzicka@redhat.com Adam Ruzicka
              Lukas Hellebrandt Lukas Hellebrandt
              Aneta Šteflová Petrová Aneta Šteflová Petrová
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: