Ok, here is better example. We use this class to cleanup some systems. Cut from our site.pp I could not figure out how to realize it whith smart variables.

node server_1{

cleanup_2::cleanup {"/var/log/":
        matches    => ["zmd-messages.log.*", "zypper.log-*", "net-snmpd*", "warn*", "zmd-backend", "mail*", "log.*.old", "log.winbind-*.bz2", "*.bz2", "*.bz2-*", "*.log"], 
        recurse    => true, 
        size    => "100m", 
        age        => "4w",
        rmdirs    => false,
    }

cleanup_2::cleanup {"/var/puppet/clientbucket":
        matches    => "*", 
        recurse    => true, 
        size    => "50m", 
        age        => "12w",
        rmdirs    => true,
    }
    include cleanup_2
}

which version of foreman are you using? my guess is that you are using a version before parameterize class support was introduced?

Jan - is the cleanup_2::cleanup actually a define() rather than a parameterised class? Defines can be used multiple times, so that's what it looks like to me, while a class (even parameterised) can only be included once. If you could paste the start of the cleanup declaration that'd be useful to clarify.

Yes, it is a define. Of course you can include a class only one times. Sorry for the bad explanation. Here is the complete class.

class cleanup_2 {
    define cleanup ($matches, $age, $size, $recurse, $rmdirs) {
        tidy {"$name":
            matches    => $matches, 
            age    => $age, 
            size    => $size, 
            recurse    => $recurse, 
            backup    => false,
            rmdirs    => $rmdirs;
        }
    }
}

Suggestion:

As said on http://projects.theforeman.org/projects/foreman/wiki/Instantiate_Puppet_resources

We can create a module for all wrappers

then for every define we want we just need to create a manifest, always with the same content.

For example, to be able to instantiate bind::server::conf of this module: https://forge.puppetlabs.com/thias/bind

We can create /etc/puppet/environments/production/modules/wrappers/manifests/bind/server/conf.pp with this content:

class wrappers::bind::server::conf($resources = {}) {
  create_resources('bind::server::conf', $resources)
}

Then on foreman we can include that new class and for resource parameter we can provide this hash:

/etc/named.conf:
  listen_on_addr:
  - any
  listen_on_v6_addr:
  - any
  forwarders:
  - 8.8.8.8
  - 8.8.4.4