-
Notifications
You must be signed in to change notification settings - Fork 23.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do a better job identifying Python locations when connection is local #44173
Comments
Files identified in the description: If these files are inaccurate, please update the |
We are looking into this. It will likely not be default behavior, and will require a toggle within the playbook, and potentially the config to enable searching for the interpreter. A little bit of work has gone into this recently in #42783 |
FYI, the official FreeBSD port changes the default to /usr/local/bin/python, so it depends on your installation method. |
ansible |
Files identified in the description:
If these files are inaccurate, please update the |
!component -lib/ansible/modules/cloud/cloudstack/cs_configuration.py |
Files identified in the description: If these files are inaccurate, please update the |
Fixed in #50163 |
SUMMARY
The Ansible BSD documentation currently requires users to explicitly configure the Python interpreter path:
https://docs.ansible.com/ansible/2.5/user_guide/intro_bsd.html
This is annoying, especially when a perfectly good Python interpreter is already available in
$PATH
. Ansible could do a better job integrating with BSD and other*nix
systems, such:ISSUE TYPE
COMPONENT NAME
ansible-playbook
SUGGESTED REMEDIATION STEPS
/usr/bin/python
and simply usingpython
instead. This would allow Ansible to succeed for many more operating system environments by default.ansible_python_interpreter
, such as/usr/local/bin/python
for FreeBSD. Have user inventories extend this default inventory configuration.ansible-playbook
is running on BSD machines, and apply the correct hardcoded absolute path, such as/usr/local/bin/python
in FreeBSD. Playbooks are already capable of switching on OS metadata. The base Ansible CLI tools should be able to do this as well.Any or all of these changes would make for a better out-of-the-box experience with Ansible with BSD machines.
The text was updated successfully, but these errors were encountered: