On Thu, Mar 6, 2014 at 10:16 PM, Jeff McCune <[email protected]> wrote:
> This is just a continuation of a previous thread as to not hijack the > original discussion. > > The question that needs a decision is, should post_resource_eval be > renamed given the context that it's currently implemented as a hook into > the point after all resources for a provider are evaluated and we might > want a hook into the point after each discrete resource is evaluated? > > Nan agrees it should be renamed hence the need for a decision. > I'm not sure where this should be documented (is there a ticket?). There is one more challenge for post_resource_eval v.s. post_catalog_eval. I believe there is a need to be able to establish a dependency to post_resource_eval. resource_type_a resource_type_a ... resource_type_a_post_resource_eval resource_type_b (can I require resource type A's post resource eval?) Thanks, Nan -- 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/CACqVBqAYocs%3DNOs%3Dj28bfogrd%2B0fyFKp3HjPX8_p2y1TXaWnZg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
