mirror of
https://github.com/ansible/ansible.git
synced 2026-08-03 08:03:05 +02:00
* Code-block wrapping for playbooks_startnstep.rst #75934 Co-authored-by: Abhijeet Kasurde <akasurde@redhat.com>
This commit is contained in:
co-authored by
Abhijeet Kasurde
parent
5c4bbed2de
commit
22a540e109
@@ -11,7 +11,9 @@ When you are testing new plays or debugging playbooks, you may need to run the s
|
||||
start-at-task
|
||||
-------------
|
||||
|
||||
To start executing your playbook at a particular task (usually the task that failed on the previous run), use the ``--start-at-task`` option::
|
||||
To start executing your playbook at a particular task (usually the task that failed on the previous run), use the ``--start-at-task`` option.
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
ansible-playbook playbook.yml --start-at-task="install packages"
|
||||
|
||||
@@ -22,11 +24,15 @@ In this example, Ansible starts executing your playbook at a task named "install
|
||||
Step mode
|
||||
---------
|
||||
|
||||
To execute a playbook interactively, use ``--step``::
|
||||
To execute a playbook interactively, use ``--step``.
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
ansible-playbook playbook.yml --step
|
||||
|
||||
With this option, Ansible stops on each task, and asks if it should execute that task. For example, if you have a task called "configure ssh", the playbook run will stop and ask::
|
||||
With this option, Ansible stops on each task, and asks if it should execute that task. For example, if you have a task called "configure ssh", the playbook run will stop and ask.
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
Perform task: configure ssh (y/n/c):
|
||||
|
||||
|
||||
Reference in New Issue
Block a user