Jira (PUP-7276) defined types in Puppet 4 (or 3.8 future parser) lost access to scope of calling class

Zed Pobre (JIRA) Mon, 27 Feb 2017 17:01:59 -0800

Title: Message Title

Zed Pobre commented on

PUP-7276

As an example of the logic I use, here's a stripped down version of one of my common cases much of the logic omitted, but you can see where it's going:

define myclass::templatemacro (

    $ensure = 'present',

    $module = $caller_module_name,

    $feature = undef,

    $feature2 = undef,

) {

    # ... insert logic here to autodetect final values based on things like $feature and

    # the detected or specified module and various functions that detect the presence

    # of files in different modules on the puppetserver ...

    $realtemplate = "${real_module}${prepended_path}${title}${suffix}"

    file { $title :

        ensure  => $ensure,

        owner   => 'root', group => 'root', mode => '0600',

        content => template($realtemplate),

Any class in any module can then call myclass::templatemacro

{ 'filepath': }

and have it put the appropriate matching file on the filesystem, even if the template source for it wasn't in their own module, wasn't even a template and needed to not be parsed, etc. It's a very compact syntax that enforces a very specific layout in the templates/ and files/ areas (always exact match to where it ends up on the filesystem, plus a potential prefix path and suffix on the filename) that makes auditing quite simple. I never have to look up where the source of a template was in a particular class – I only have to figure out what module was in use and what the computed prefix and suffix was, which is usually pretty obvious at a glance because there aren't very types of things people key on, and the autodetect rules are pretty simple.

Add Comment

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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7276) defined types in Puppet 4 (or 3.8 future parser) lost access to scope of calling class

Reply via email to