Issue #2408 has been updated by Nigel Kersten.
We don't have a clear plan for directly adding resources from an ENC, so working on defining that plan would be a huge help :) It's a reasonably large behavior change to make an ENC now support adding resources directly (including their parameters) rather than just saying what classes should be added. Note the workaround is to pass node parameters for use with classes that use those parameters to instantiate the resources. It's at least one too many abstraction layers... but does work :( ---------------------------------------- Feature #2408: It should be possible to assign a definition to a node in an external nodes tool https://projects.puppetlabs.com/issues/2408 Author: Pieter Barrezeele Status: Accepted Priority: High Assignee: Category: Target version: Telly Affected Puppet version: 0.24.8 Keywords: Branch: Until now, only classes/modules and parameters can be assigned to nodes in an external nodes tool. It would be very useful to be able to assign a definition, such as: <pre> node ws1 inherits webserver { apache::vhost{"www.example.com"} } </pre> to a node using yaml. The only other way to do now, seems to be writing wrapper classes. Thanks, Pieter. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
