Jira (PUP-1606) Virtual classes are always realized

Adam T Backer (JIRA) Wed, 22 Oct 2014 14:58:35 -0700

Title: Message Title

Adam T Backer commented on an issue

I've created a workaround using this pattern, but it obviously has a required level of maintenance on the defined type that is undesirable. This will work in the interim, but I will not entertain the idea of releasing my Nagios module in this state.

Cheers,

  1 class vclass ($var1 = 'blah', $var2 = 'blerf') {

  2   notify {"vclass":

  3       message => "I've been realized as ${title}: var1 => ${var1} - var2 => ${var2}"

  4   }

5 }

  7 class iclass {

  8   define idef (

  9     $var1 = 'true',

 10     $var2 = 'false') {

 11       class { "vclass":

 12           var1 => $var1,

 13           var2 => $var2,

 14         }

 15     }

 17 }

 19 class xclass {

 20   class { 'iclass': }

 21   @iclass::idef { 'test':

 22     var1  => 'var1',

 23   }

 25   Iclass::Idef <| title == 'test' |> {

 26     var2  => 'var2',

 27   }

 28 }

 30 class {"xclass":}

Add Comment

Puppet /

PUP-1606

Declaring a virtual class should not instantiate it without being realized. This worked in puppet 2.6.1 but is broken in 2.6.7. I also tried it in 2.7.9 and it still seems to be broken. The code below is a very simple example. vclass and the notify should not happen because it is not realized.

{code}
class vclass {
notify {"vclass":
...

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-1606) Virtual classes are always realized

Reply via email to