Red Hat Ansible Automation Platform Controller Licensing, Updates, and Support 1.1. Automation Controller Administration Guide v4.2.2 1. And I don't want contains IPs if a no_ptr_record: true variable is defined (false or not defined is ok). Find the Automation Controller documentationset which best matches your version of the controller. I tried json_query() and selectattr() filters but I'm struggling on the fact that not every host entry has IPv4 or IPv6 addresses defined. I have ansibledevices variable in json format, and i want to get only some disks names list with specific size, i tried to use jsonquery with filter from this howto, but cant get my data. I'm pretty sure this can be solve smarter :Dīasically I just need list of all IPs of all zones. I double loop over dns_zone_config and their host entries. When: item.ip is defined and (item.no_ptr_record is not defined or not item.no_ptr_record) Note: Any remoteuser defined in tasks will be ignored. It dynamically creates an Ansible inventory file configured to use SSH, runs an SSH server, executes ansible-playbook, and marshals Ansible plays through the SSH server to the machine being provisioned by Packer. When: item_dns_zone_config.hosts is defined The ansible Packer provisioner runs Ansible playbooks. My current way looks like: - name: Collect all networks The first step is hitting the root endpoint of API to get a list of users: The above block will get the list of users which gets stored in userlist variable using uri module of Ansible. The forward-lookup zone variable should look like dns_zone_config:ĭns_zone_config is a list of dictionaries that may contains a key called "hosts" which is again a list of dictionaries. Reverse-lookup zones (0.0.10.in-appr.arpa) should be auto-generated with Ansible. The user should just maintain one variable for the forward-lookup zones (e.g. I'd like to build our DNS zones via Ansible.
0 Comments
Leave a Reply. |