Issue #4523 has been updated by James Turnbull. Target version set to 2.6.1
---------------------------------------- Bug #4523: ::classname resolution does not work as expected http://projects.puppetlabs.com/issues/4523 Author: Matt Robinson Status: Unreviewed Priority: Normal Assigned to: Category: Target version: 2.6.1 Affected version: testing Keywords: scope Branch: While working on Dashboard I was trying to figure out what class name formats should be allowed, and assumed that classes preceded by :: shouldn't be in dashboard since Puppet would just make those classes available at topscope with their bare name. For example: class ::foo { file {'/tmp/foo': ensure => present, } notice("foo") } I assumed you could do include foo On 2.6, 0.25.5 and testing 8ddea2: Could not find class foo at /root/work/puppet/test.pp:7 on node ubuntu1004desktop.localdomain However if I do include ::foo On 2.6: notice: Scope(Class[::Foo]): foo On testing 8ddea2 and 0.25.: Invalid tag "::foo" at /root/work/puppet/test.pp:7 on node ubuntu1004desktop.localdomain I'm not sure what the expected behavior is by someone more familiar with this scoping, but I'm not sure based on these results how class ::foo should be included or what to do in dashboard. -- 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.
