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

Add support for using a http proxy when syncing templates

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • Add support for using a http proxy when syncing templates
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • SAT-19573 - Full support for IPV6
    • 0
    • 11% To Do, 89% In Progress, 0% Done
    • Endeavour
    • Proposed

      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:
              2 Start watching this issue

                Created:
                Updated: