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

include order decides tagged actions

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Do
    • Affects Version/s: PUP 5.4.0
    • Fix Version/s: None
    • Component/s: Language
    • Labels:
      None
    • Environment:

      Ubuntu 18.04

    • Template:
      PUP Bug Template
    • Acceptance Criteria:
      Hide

      "/bin/echo after" runs regardless of the include ordering

      Show
      "/bin/echo after" runs regardless of the include ordering
    • Sub-team:
    • Team:
      Platform Core
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      class mytype::after {
              @exec {'/bin/echo after': }
      }
       
      define mytype () {
              contain mytype::after
              realize Exec['/bin/echo after']
              exec {"/bin/echo mytype $title": }
              -> Exec['/bin/echo after']
      }
       
      class apache {
              mytype {'apache': }
              -> exec {'/bin/echo apache last': }
      }
       
      class ntp {
              mytype {'ntp': }
              -> exec {'/bin/echo ntp last': }
      }
       
      include apache, ntp
      

      Given these definitions, running
      puppet apply --tags apache
      will run '/bin/echo after'.
      puppet apply --tags ntp
      will not.
      Reversing the include statement to
      include ntp, apache
      will do the opposite.
      I would expect all cases to run the "/bin/echo after".

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            0xfedcba Mike Jonkmans
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support