Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-9566

Allow to send extra headers when requesting a catalog compilation

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 6.14.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Epic Link:
    • Team:
      Coremunity
    • Sprint:
      Platform Core KANBAN
    • Release Notes:
      Enhancement
    • Release Notes Summary:
      Users can now define custom headers to send with http requests to puppet infrastructure. Use the `:http_extra_headers` setting to define these. They should be a comma separated string of `key:value` pairs.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Pointing a set of Puppet Agents to different Puppet Servers is only possible by changing the "server" or "port" values in the puppet.conf. In this new approach, we are trying to deploy our servers in a Kubernetes cluster and point all the agents to the same server and port (the cluster's Ingress). For this to work, we need a mechanism to indicate where the traffic should be redirected. The easiest way to do this is by setting a header in the Puppet Agent's request.

      This change will allow to set extra headers to be send every time Puppet Agent is executed on the node. Our set up is just a use case for this new feature but the community could also benefit form it.

        Attachments

          Activity

            People

            Assignee:
            melissa Melissa Stone
            Reporter:
            davidmogar David Moreno García
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support