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

Environment variables set in functions leak into subsequent runs

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Team:
      Coremunity
    • QA Risk Assessment:
      Needs Assessment

      Description

      If an environment variable is set within a custom function on the Puppet server, that environment variable leaks into all subsequent ENC runs and catalog compilations. We reproduced this on 2.4.0 and 2.7.1 but presumably this affects a large number of versions.

      I've posted instructions to reproduce this bug at: https://gist.github.com/kpaulisse/3ca39285e439b093126f3bcd94d93ddb

      One can definitely argue the wisdom of setting environment variables via functions... In our production environment where we noticed this problem, it was unintentional: the environment variable was being set from a script that was executed by a function.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            kpaulisse Kevin Paulisse
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support