The basic configuration items are not templatable at all as no vars
were accessible when designed, extra vars got added later for
'constructed' features.
We do have plans to make this work, specially with vaults (you can
vault the file, but not use inline vaults).
--
--
Brian Coca
--
Y
Inventory plugins can only read from ENV variables. Not sure why, but seems like a architectural limitation. Most of the inventory plugins either read from files (like AWS) or from ENV variables. Sent from my iPhoneOn 29/09/2023, at 5:17 AM, J M wrote:Many thank, works!!!Because not work with --e
Many thank, works!!!
Because not work with --extra-vars?
Regards
El jueves, 28 de septiembre de 2023 a las 18:09:18 UTC+2, Will McDonald
escribió:
> Could you use the environment variable ANSIBLE_NMAP_ADDRESS as documented
> below as an alternative?
>
>
> https://docs.ansible.com/ansible/lat
Could you use the environment variable ANSIBLE_NMAP_ADDRESS as documented
below as an alternative?
https://docs.ansible.com/ansible/latest/collections/community/general/nmap_inventory.html#parameter-address
https://docs.ansible.com/ansible/latest/collections/environment_variables.html#envvar-ANSIB
Hi,
I have a question of howto use external variables in the nmap plugin.
I have a simple yml:
plugin: nmap
address: 192.168.10.0/24
...
But I need to pass the network range as a external variable, as example:
plugin: nmap
address: '{{ mynetrange }}'
# I tested this argument also:
use_extra_vars
