On Tue, Oct 15, 2013 at 8:48 AM, Luke Kanies <l...@puppetlabs.com> wrote:
> If, in the course of implementing this, you happen to find it easy to > implement an easy way to delay resources that might not be "ready", that > would be awesome, too. That is, if there were a hook similar to those > below that could be used to see if a resource is ready to run, then > resources that aren't ready could be put into the back of the queue. This > would be useful for things like waiting to bring up services until a remote > required service is ready. > > I expect this is too large a change to shoehorn into this effort, but I > figured I'd at least bring it up. The biggest difference (both this and > batching involve delaying resources) is that this puts you in a place where > you might only have non-ready resources remaining, which is a new kind of > failure state, whereas batching packages should never result in that. > > Luke, That's an interesting use case, and not one that I'd really considered. Off the cuff, I agree that this is probably too large a change to tag along with the batch processing feature, but it's definitely in the same area of code, so it will be useful to keep this case in mind as we implement batch processing (e.g. if only so as not to make such a change harder in the future, etc). Thanks! Kylo -- 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 puppet-dev+unsubscr...@googlegroups.com. To post to this group, send email to puppet-dev@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
