This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
637 B
637 B
— ansible_ifcfg_blocklist: True
copr_hostbase: copr-fe-dev datacenter: aws description: copr frontend - dev instance hostbase: copr-fe-dev- inventory_hostname: "copr-fe-dev.aws.fedoraproject.org" inventory_instance_name: copr-fe-dev nagios_Check_Services: dhcpd: false httpd: false mail: false named: false nrpe: true ping: false raid: false sshd: false swap: false nm_controlled_resolv: True principal_alias: "HTTP/copr-fe-dev.cloud.fedoraproject.org@STG.FEDORAPROJECT.ORG" public_ip: 18.208.24.211 root_auth_users: msuchy frostyx praiskup schlupov ttomecek swap_file_path: /swap swap_file_size_mb: 4096