undefined class results in error instead of warning in 2.7.3

[Steven Seed]

My ENC has always added some extra classes not defined in puppet (things that I might end up using later based on the host name, department, or other attributes associated with the host in my database). In 0.25.5 the undefined class was reported at (info), in 2.6.9 it was reported as (warning), but in 2.7.3 it's an (err) ? This now causes my catalog to stop processing. Why the change to error now?

2.6.9:
Puppet (warning): Could not find class tech for mohogany.fas.fa.disney.com

2.7.3:
Puppet (err): Could not find class tech for mohogany.fas.fa.disney.com on node mohogany.fas.fa.disney.com

[Steven L. Seed]

I see now after trying to post a bug on this that this behavior is now by design as of 2.7. I understand the reasoning behind the change to keep the behavior consistent with including undefined classes in manifests. My problem is being an “external' node classifier, I don’t currently have a way to validate whether or not the class I’m specifying in the ENC is valid or not and as it happens, the data I’m referencing and using for class names comes from a database that has other uses besides puppet's ENC so I don't have full control over what gets in there. If I could get some suggestion on how to validate the existence of a class from my ENC then I could check them before adding them to a node. Currently the ENC is written in perl.

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/VdwBurIYVzAJ.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>