docs: get rid of "medium risk" category

wip-fakessh-exit-status
David Wilson 7 years ago
parent da00437f1e
commit 1b28252ad0

@ -82,18 +82,6 @@ High Risk
``become_user``, and ``local_action`` have all been tested. ``become_user``, and ``local_action`` have all been tested.
Medium Risk
~~~~~~~~~~~
* In some cases ``remote_tmp`` may not be respected.
* Interaction with modules employing special action plugins is minimally
tested, except for the ``synchronize``, ``template`` and ``copy`` modules.
* For now only Python command modules work, however almost all modules shipped
with Ansible are Python-based.
Low Risk Low Risk
~~~~~~~~ ~~~~~~~~
@ -104,6 +92,17 @@ Low Risk
* The only supported strategy is ``linear``, which is Ansible's default. * The only supported strategy is ``linear``, which is Ansible's default.
* In some cases ``remote_tmp`` may not be respected.
* Interaction with modules employing special action plugins is minimally
tested, except for the ``synchronize``, ``template`` and ``copy`` modules.
* For now only Python command modules work, however almost all modules shipped
with Ansible are Python-based.
* Uncaptured standard output of remotely executing modules and shell commands
are logged to the console. This will be fixed in a later version.
* Ansible defaults to requiring pseudo TTYs for most SSH invocations, in order * Ansible defaults to requiring pseudo TTYs for most SSH invocations, in order
to allow it to handle ``sudo`` with ``requiretty`` enabled, however it to allow it to handle ``sudo`` with ``requiretty`` enabled, however it
disables pseudo TTYs for certain commands where standard input is required or disables pseudo TTYs for certain commands where standard input is required or

Loading…
Cancel
Save