First, not all paths are equal nor work the same way. The execution path, which is what you are getting when running `pwd`, depends on the connection plugin, it normally is the 'login directory' which for ssh is usually the remote $HOME. For most plugins this has not changed across versions.
The 'local' connection plugin (default for localhost/local_action) had a bug introduced in 2.0 in which the path changed from 'playbook directory' to invocation path, 2.1.2 fixed that bug. This is what you are seeing in your tests, which do not really apply to the template plugin. The lookup and action plugins (like template and copy) have their own logic for finding paths (which has also had a few bugs). The way it is supposed to work is (given relative paths) to search based on role, include or playbook directory (more specific wins with fallback to parent). Also pre-pending 'files', 'vars' or 'templates' if needed and depending on the exact plugin. These are different than the 'execution path' detailed above. ---------- Brian Coca -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CACVha7ftDCdaVaKFEC3ydrp2S%2BRCXCe_S3z36Ey3qAwk6UThBg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
