Using `--start-at-task` won't work because it won't inherit the state from the beginning of the playbook. So facts that were set earlier will be undefined.
On Fri, May 6, 2016 at 3:41 AM Johannes Kastl <[email protected]> wrote: > On 05.05.16 23:36 Neil Hooey wrote: > > > When initially trying to get an elaborate playbook to work, it's very > > costly to repeat the process when a single task fails. > > > Are using `retry` files the right way to do this, or is there another > way? > > --start-at-task > > https://docs.ansible.com/ansible/playbooks_startnstep.html > > Johannes > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Ansible Project" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ansible-project/G2259BohHE0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/572C4A92.2010608%40ojkastl.de > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CANFtSwiBcCpV1Ftp-RCG3D0wwTxA6XqhHGZWixb4_StQwUWTBA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
