We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is there a reason to install the file utils/cisco_imc.py in the ansible module_utils directory? Why not rename the directory utils to module_utils?
According to https://docs.ansible.com/ansible/latest/dev_guide/developing_module_utilities.html the import is dynamic and when using ansible-playbook it will merge the contents of the local module_utils (in the playbook) into ansible.module_utils namespace.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there a reason to install the file utils/cisco_imc.py in the ansible module_utils directory?
Why not rename the directory utils to module_utils?
According to https://docs.ansible.com/ansible/latest/dev_guide/developing_module_utilities.html the import is dynamic and when using ansible-playbook it will merge the contents of the local module_utils (in the playbook) into ansible.module_utils namespace.
The text was updated successfully, but these errors were encountered: