yep. exactly the case. at the moment this logic is implemented using .sh script.. so looks like the best option is to mix .sh with ansible (for pure deployment tasks). Will take a look into Fabric .. though I'd like to avoid introducing new tool for every simple task :)
On Wednesday, 25 June 2014 16:01:57 UTC-5, Dmitry Makovey wrote: > > does that mean you're running cross-host function that takes params from A > and B and returns value on B? And you expect certain value on B before you > move forward? I'm not an expert but it doesn't seem to be Ansible domain. > Maybe Fabric would be a better fit? > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/63014730-309e-44a9-b2c6-400b9a7d5388%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
