Issue #3049 has been updated by Jeff Behl.
This is a bug in that using the all_tags array (or classes array, for that matter) in a template is definitely not resulting in all tags being inserted. in the client_yaml/catalog/<hostname>.yaml file I see my class defined under 'tags:' as well as under 'classes:' yet it will not make it into the template unless the class is explicitly defined on the node. If it's a part of an 'include <class>' it doesn't make it. very aggravating. we were hoping to use this feature extensively. I'm using client and server 25.4 ---------------------------------------- Bug #3049: Several bits of the language are order dependant http://projects.puppetlabs.com/issues/3049 Author: R.I. Pienaar aka Volcane Status: Needs design decision Priority: Normal Assigned to: Markus Roberts Category: language Target version: Affected version: 0.25.4rc1 Keywords: Branch: I am filing this as a bug, could be a feature request too? anyway, puppet is pointedly a order independent language this is a major tenant of how things work and how manifests gets constructed, nodes populated and so forth - this is probably a discussion on its own but thats my view. Assuming we agree its all independent of order then functions like defined() should not exhibit weird behavior that is order dependent, this bug is to fix those. Same holds true for inside templates the variables all_tags and classes -- 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.
