John, Again, very helpful... My knowledge of puppet is growing every day thanks to posts like this :-)
Cheers Gavin On Nov 26, 2012 7:30 PM, "jcbollinger" <john.bollin...@stjude.org> wrote: > > > On Monday, November 26, 2012 12:19:09 PM UTC-6, Gavin Williams wrote: >> >> John >> >> Cheers again, that could be a good alternative way of doing it... Use >> insync? just to trigger options=, and then work out what actually needs >> setting there... >> > > That's not just a good alternative, it's the right way to do it. The job > of insync? is simply to determine whether all of the resource's properties > have the expected target values. No more, no less. The job of property > setter methods such as options= is to update the underlying resource(*) so > that the affected property has the assigned value. It is there, at the > interface between Puppet and the system, that you have flexibility. > > (*) The property setters of providers that implement flush() work a bit > differently, but I don't think that's relevant here. I mention it for > completeness. > > > John > > -- > 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/-/OEk9ZWDBvWUJ. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
