"Fossies" - the Fresh Open Source Software Archive 
Source code changes of the file "docs/docsite/rst/playbook_guide/playbook_pathing.rst" between
ansible-2.14.0.tar.gz and ansible-2.14.1rc1.tar.gz
About: Ansible is an IT Configuration Management, Deployment & Orchestration tool. Release candidate.
| playbook_pathing.rst (ansible-2.14.0) | : | playbook_pathing.rst (ansible-2.14.1rc1) | ||
|---|---|---|---|---|
| skipping to change at line 17 | skipping to change at line 17 | |||
| You can control the paths Ansible searches to find resources on your control nod e (including configuration, modules, roles, ssh keys, and more) as well as resou rces on the remote nodes you are managing. Use absolute paths to tell Ansible wh ere to find resources whenever you can. However, absolute paths are not always p ractical. This page covers how Ansible interprets relative search paths, along w ith ways to troubleshoot when Ansible cannot find the resource you need. | You can control the paths Ansible searches to find resources on your control nod e (including configuration, modules, roles, ssh keys, and more) as well as resou rces on the remote nodes you are managing. Use absolute paths to tell Ansible wh ere to find resources whenever you can. However, absolute paths are not always p ractical. This page covers how Ansible interprets relative search paths, along w ith ways to troubleshoot when Ansible cannot find the resource you need. | |||
| .. contents:: | .. contents:: | |||
| :local: | :local: | |||
| Config paths | Config paths | |||
| ============ | ============ | |||
| By default these should be relative to the config file, some are specifically re lative to the current working directory or the playbook and should have this not ed in their description. Things like ssh keys are left to use the current workin g directory because it mirrors how the underlying tools would use it. | By default these should be relative to the config file, some are specifically re lative to the current working directory or the playbook and should have this not ed in their description. Things like ssh keys are left to use the current workin g directory because it mirrors how the underlying tools would use it. | |||
| .. _playbook_task_paths: | ||||
| Task paths | Task paths | |||
| ========== | ========== | |||
| Relative paths used in a task typically refer to remote files and directories on the managed nodes. However, paths passed to lookup plugins and some paths used in action plugins such as the "src" path for the :ref:`template <ansible_collect ions.ansible.builtin.template_module>` and :ref:`copy <ansible_collections.ansib le.builtin.copy_module>` modules refer to local files and directories on the con trol node. | Relative paths used in a task typically refer to remote files and directories on the managed nodes. However, paths passed to lookup plugins and some paths used in action plugins such as the "src" path for the :ref:`template <ansible_collect ions.ansible.builtin.template_module>` and :ref:`copy <ansible_collections.ansib le.builtin.copy_module>` modules refer to local files and directories on the con trol node. | |||
| Resolving local relative paths | Resolving local relative paths | |||
| ------------------------------ | ------------------------------ | |||
| When you specify a relative path for a local file, Ansible will try to find that file first in the current task's role, then in other roles that included or dep end on the current role, then relative to the file in which the task is defined, and finally relative to the current play. It will take the first matching file that it finds. This way, if multiple files with the same filename exist, Ansible will find the file that is closest to the current task and that is most likely to be file you wanted. | When you specify a relative path for a local file, Ansible will try to find that file first in the current task's role, then in other roles that included or dep end on the current role, then relative to the file in which the task is defined, and finally relative to the current play. It will take the first matching file that it finds. This way, if multiple files with the same filename exist, Ansible will find the file that is closest to the current task and that is most likely to be file you wanted. | |||
| End of changes. 1 change blocks. | ||||
| 0 lines changed or deleted | 2 lines changed or added | |||