Issue #23270 has been reported by Nick Weiler. ---------------------------------------- Feature #23270: Notification Without Ordering https://projects.puppetlabs.com/issues/23270
* Author: Nick Weiler * Status: Unreviewed * Priority: Normal * Assignee: * Category: newfeature * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- The current notification operator creates an ordering relationship. In certain cases this causes problems with dependency cycles. Example: Say I want to add a logging.properties file to a tomcat webapp instance. The exploded directory won't be created unless the service is running. Thus according to puppet, the file requires the service. After the file is created I want to restart the service so that the new config is picked up. Thus, the file notifies the service. But according to puppet, this also means that the service requires the file. Combine this with the statement above and I have a dependency cycle. By creating a notify without an implied order, these types of cycles can be overcome. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
