Issue #19871 has been updated by Matthaus Owens. Project changed from Puppet Enterprise (Public) to Puppet
As this is not a PE specific feature, and rather a Puppet one, I've moved this to the Puppet project. ---------------------------------------- Feature #19871: Templates Shouldn't Cause Runs To Fail https://projects.puppetlabs.com/issues/19871#change-87577 * Author: Celia Cottle * Status: Unreviewed * Priority: Normal * Assignee: * Category: * Target version: * Affected Puppet version: * Keywords: customer * Branch: ---------------------------------------- A customer submitted the following feature request: Currently all templates are generated during catalog compilation phase. If for whatever reason any template cannot be generated fatal error is thrown and Puppet fails during catalog compilation - nothing gets done. This seems like a design flaw to me as sometimes on purpose we do not want to generate template if eg. certain fact is not present (so file does not get updated) whereas we still want to be able to run Puppet to eg. fix the issue. This easily can lead to deadlock situations when certain template cannot be generated because certain fact is not present and Puppet run is required to cure it. Would it be possible to fail templates in the very same manner as other resources (eg. files), so only dependent resources get affected and not everything. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
