You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if there are plans to implement environment variable support for username/password within the nimble modules?
A good example is all of the VMWare modules which take the username, password, and hostname via Ansible fields, but also can accept VCENTER_USERNAME, VCENTER_PASSWORD, VCENTER_HOSTNAME respectively. This does make it easier to pass credentials from tools like Ansible Tower and AWX more securely in my opinion.
The text was updated successfully, but these errors were encountered:
Thanks @coltonhughes! This is an excellent RFE in my opinion as it will reduce clutter in the tasks. I'll bring this to the team for consideration. In the meantime you can use the lookup plugin for the task credentials. {{ lookup('env', 'NIMBLE_PASS') }} if you're blocked waiting for this functionality.
No problem. Always trying to help throw (potentially) helpful ideas around to make modules the most consistent and user friendly. Luckily I am not blocked currently but that is an excellent solution in case somebody else stumbles across this as well. Thanks for the quick response and feel free to close, or mark this ticket however you need to.
I was wondering if there are plans to implement environment variable support for username/password within the nimble modules?
A good example is all of the VMWare modules which take the username, password, and hostname via Ansible fields, but also can accept VCENTER_USERNAME, VCENTER_PASSWORD, VCENTER_HOSTNAME respectively. This does make it easier to pass credentials from tools like Ansible Tower and AWX more securely in my opinion.
The text was updated successfully, but these errors were encountered: