-
Notifications
You must be signed in to change notification settings - Fork 141
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
Replaced #!/usr/bin/env python
with #!/usr/bin/python
#509
base: master
Are you sure you want to change the base?
Conversation
@AllRWeak, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
@AllRWeak, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
…sible module format Signed-off-by: Allar Viik <allar@clarifiedsecurity.com>
When will this PR get merged? |
@ggverma when will this be merged? |
When will this be merged? |
Staring from Ansible 2.17.1 modules in this collection are unable the find the Python interpreter. According to This issue ansible/ansible#83603 and Ansible development guide https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_documenting.html#python-shebang-utf-8-coding all modules should start with
#!/usr/bin/python
This PR replaces
#!/usr/bin/env python
with#!/usr/bin/python
in all modules to make sure they match with Ansible module format and fixes #508This fix has also been tested on Ansible 2.17.0 to make sure it's also backwards compatible.