Skip to content

Commit 1c5251d

Browse files
Add network differences explanation (#1051)
* add network differences description * Update docs/docsite/rst/network/getting_started/network_differences.rst Co-authored-by: Felix Fontein <[email protected]> --------- Co-authored-by: Felix Fontein <[email protected]>
1 parent 42e07a1 commit 1c5251d

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/docsite/rst/network/getting_started/network_differences.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ Unlike most Ansible modules, network modules do not run on the managed nodes. Fr
1414

1515
Network modules also use the control node as a destination for backup files, for those modules that offer a ``backup`` option. With Linux/Unix modules, where a configuration file already exists on the managed node(s), the backup file gets written by default in the same directory as the new, changed file. Network modules do not update configuration files on the managed nodes, because network configuration is not written in files. Network modules write backup files on the control node, usually in the `backup` directory under the playbook root directory.
1616

17+
When using the connection plugins (for example, ``ansible.netcommon.network_cli``) for network modules, Unix/Linux modules such as ``ansible.builtin.file`` and ``ansible.builtin.copy`` also run on the control node.
18+
1719
Multiple communication protocols
1820
================================================================================
1921

0 commit comments

Comments
 (0)