On Jan 24, 10:02 am, Peter Meier <[email protected]> wrote: > I think this is a general problem with puppet providers that will call > services that will finish the task asynchronously. So I'm asking myself > if there are any best practices to deal with such interfaces? Should > puppet actually be able to deal with this kind of calls? Or is the fire > and forget solution the appropriate one.
There are a couple of branches and ideas out there for dealing with async resources. I don't recall specifics off hand though. Luke? Personally I ran in to the same issue with a provider I wrote for AWS Route 53. Unfortunately, I ended up ignoring the issue. I figure having a node that never reaches stable state is pretty much an error itself. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
