* fix rstcheck errors for 6.1.1
* spell shell correctly
pull/79953/head
Sandra McCann 1 year ago committed by GitHub
parent 0793833847
commit dc99005820
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -388,8 +388,8 @@ Here is a simple mock of :meth:`AnsibleModule.run_command` (taken from :file:`te
with patch.object(basic.AnsibleModule, 'run_command') as run_command:
run_command.return_value = 0, '', '' # successful execution, no output
with self.assertRaises(AnsibleExitJson) as result:
my_module.main()
with self.assertRaises(AnsibleExitJson) as result:
my_module.main()
self.assertFalse(result.exception.args[0]['changed'])
# Check that run_command has been called
run_command.assert_called_once_with('/usr/bin/command args')

@ -91,7 +91,7 @@ The playbook sets three of the seven values from the command line above: the gro
The playbook contains one play with two tasks, and should generate output like this:
.. code-block:: bash
.. code-block:: shell
$ ansible-playbook -i vyos.example.net, -u ansible -k -e ansible_network_os=vyos.vyos.vyos first_playbook.yml
@ -115,7 +115,7 @@ The playbook contains one play with two tasks, and should generate output like t
The extended first playbook has five tasks in a single play. Run it with the same command you used above. The output shows you the change Ansible made to the config:
.. code-block:: bash
.. code-block:: shell
$ ansible-playbook -i vyos.example.net, -u ansible -k -e ansible_network_os=vyos.vyos.vyos first_playbook_ext.yml

Loading…
Cancel
Save