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

Setting enc paramater environment seems to corrupt the internal environment paramater.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Incomplete
    • Affects Version/s: PUP 3.8.5
    • Fix Version/s: None
    • Component/s: Language
    • Labels:
    • Environment:

      Testing an upgrade from 3.8.4 to 3.8.5 with a puppet master and custom ENC script.

    • Template:
    • Team:
      Coremunity

      Description

      We have been using Puppet for several years, back when Puppet was not setting a top-scope environment parameter, so our custom ENC script would to this. When testing the latest 3.8.5 version of Puppet, we discovered that when the ENC was setting this top-scope environment parameter, it would appear to corrupt it somehow. It could still be used in templates and strings, but if it was used in a logical expression, like:

      if ($::environment == 'production') {
        ...
      }
      

      it would fail to match the string comparison. I tested it with the type3x() function from stdlib and it was an unknown type. Since this is new in 3.8.5, I assume it has something to do with the change made in PUP-5522. Since puppet now sets the environment parameter I will remove it from our ENC script, but since just setting an environment parameter in the ENC source data now seems to corrupt it, I thought I should still report this as a bug.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            smithj4 Jason A. Smith
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support