I have not heard of that option before, but in any case, the docs on it ( https://docs.ansible.com/ansible/latest/user_guide/playbooks_startnstep.html#start-at-task) state:
> This feature does not work with tasks inside dynamically re-used roles or tasks Also it uses dashed "--start-at-task" instead of what you use "--start.at-task" (dot) On Mon, 29 Nov 2021 at 10:51, dulhaver via Ansible Project < [email protected]> wrote: > hy everybody, > > I am trying a barman installation via Ansible which makes use of 4 roles. > > Now I want to skip most of the tasks and utilize --start.at-task "name of > a task". I am running into a 'task not found' error. > I tried variants like --start.at-task "role name"/"name ot a task" > without any luck. > > So, do I get the syntax wrong or is there any secret sauce needed when > working in a role based scenario, or is --start-at-task simply not made > for roles? > > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/1655872842.380705.1638179448319%40office.mailbox.org > <https://groups.google.com/d/msgid/ansible-project/1655872842.380705.1638179448319%40office.mailbox.org?utm_medium=email&utm_source=footer> > . > -- Dick Visser Trust & Identity Service Operations Manager GÉANT -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAL8fbwOw8JBj4dWFx42u8enVPF-t-0LrgGophd7quDWmpoqbSw%40mail.gmail.com.
