[PR #1718/90766243 backport][stable-2.17] add note about arguments in shebang in modules #1773
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![patchback[bot]](https://avatars.githubusercontent.com/in/21488?s=60&v=4){kind=small}
* add note about arguments in shebang in modules * update note about arguments in shebang in modules * move notes about shebang in one warning (cherry picked from commit 9076624)
oraNod
approved these changes
Aug 21, 2024
oraNod
deleted the
patchback/backports/stable-2.17/90766243510da5f78cb8fbf69ff409a6748e327d/pr-1718
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #1718 as merged into devel (9076624).
In ansible/ansible#83603 the result of the discussion was that it is neither wanted nor supported to use arguments in the shebang.
Obviously, this feature is not a matter of common knowledge. I'm far from the only one who didn't know that. (e.g. VMware's NSX-T Ansible Modules or even the test-playbook from ansible itself)
imho this is also due to ambiguous documentation.
With this PR, I would like to make the documentation a little clearer. I'm always open to suggestions for improvement.