On Saturday, January 4, 2014 7:50:17 PM UTC-6, Trevor Vaughan wrote: > > You could also have two custom types, one that creates keys and one that > purges. The ones that create/manage, can be autorequired by the one that > purges. > > Alternatively, you can use 'flush' to only purge when the last key > management type is executed on the system. > > It's a bit cumbersome, but the general idea can be found at > https://www.onyxpoint.com/storing-puppet-provider-metadata-for-single-instance-application/ > . > >
Using the group flush approach as per the example, with the agent running in daemon mode, do the added provider class variables (@@demo_classvars in the example) persist from one catalog run to the next? Also, am I wrong in thinking that if one resource in a group related via such a mechanism is not applied (e.g. because it 'require's a failed resource) then the whole group's final flush will never be triggered? I'm just trying to understand the implications. John -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/53453861-0603-4281-b292-90e596cfb269%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
