On Friday, March 3, 2017 at 11:30:42 AM UTC-6, Peter Kristolaitis wrote: > > A subscribed / notified resource will only trigger once. Puppet's basic > execution model only allows each resource to run once during a catalog run, > and you can think of notify/subscribe as a special case of using 'require' > to determine execution order. >
That's not quite right. A resource will be *synced* at most once during each catalog run, and it will *also* be *refreshed* at most once. Most resources that have non-trivial refresh actions do something different when refreshed than when synced -- for example, Service resources restart. By default, however, Execs have the same sync and refresh actions: to run their command. Thus, the command of an Exec can be run twice in a catalog run. Fortunately for the OP, however, the effect of declaring an Exec "refreshonly" is effectively to change its sync action from running the Exec's command to a no-op. In his specific case, therefore, his Execs' commands will run at most once per catalog run. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/19e7ce2f-0b19-42ae-bb90-dc5c0444a5ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
