Jira (PUP-6800) Better error messaging around invalid class names

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on PUP-6800   Re: Better error messaging around invalid class names The example looks more like a bug since class references are supposedly case independent. The fact that it worked a second time seems to indicate that this has nothing to do with the class name per se. I can imagine though that first vs. second time could lead to a different path through the logic and that there may be something wrong on the path used the first time - say using create_resources vs. something else - conditional logic written differently etc. IIRC, there has also been bugs related to case independent references that are now fixed - so, puppet version used matters here. Can you supply a simple self contained reproducer? Note that 'role::appserver::windows_2012R2' does not break the naming convention - it is ok to have underscores, digits and upper case letters as long as those are not the first in a name segment. This means that the issue here is not about "better errors when naming convention is broken", but something else. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.