This website requires JavaScript.
Explore
Help
Sign in
infrastructure
/
ansible
Watch
1
Star
0
Fork
You've already forked ansible
0
Code
Pull requests
7
Activity
Actions
dc139f3f6a
ansible
/
inventory
/
group_vars
/
cloud
7 lines
87 B
Text
Raw
Normal View
History
Unescape
Escape
do we need --- in vars?
2017-05-01 21:36:03 +00:00
---
Inventory group/host variables: Sort yaml 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>
2021-11-16 13:27:57 -08:00
datacenter: cloud
Killed trailing spaces in group/host vars with fire. Normally it's just a nitpick to not have trailing spaces on variables. However, for some things like mac address, it really matters. Bunches of buildhw's were failing ansibile because they were passing "mac address " to linux-system-roles networking and ansible was going 'huh, nope, I can't find that mac address here at all'. So, just blow all the tailing spaces away to avoid any other variables that hit this. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-05-04 08:52:52 -07:00
nagios_Check_Services:
and this should make our mail easier to read
2018-08-27 22:44:54 +00:00
mail: false
and we need to fix
2017-05-01 20:10:56 +00:00
nrpe: false
try and teach nagios about hosts we want to monitor swap on and ones we do not want to
2017-09-09 19:11:06 +00:00
swap: false
Copy permalink