summaryrefslogtreecommitdiff
path: root/files/pnp4nagios/pnp4nagios-templates.cfg
diff options
context:
space:
mode:
authorMicah <micah@riseup.net>2015-05-07 15:09:55 +0000
committerMicah <micah@riseup.net>2015-05-07 15:09:55 +0000
commit18e63a63f123f580ed2f4b6747e55476c2d72413 (patch)
tree5cd8b4f15b0926e785ce367bd46b8f8d9956b5c6 /files/pnp4nagios/pnp4nagios-templates.cfg
parent40f247d6c7c4183d32452d9f4791821b92ac16c1 (diff)
parent29c61a62a49f042678a16331e2fd67bb7ae1ee57 (diff)
Merge branch 'no_alias_for_host' into 'master'
stop defining an alias by default for hosts Since the "alias" attribute is special for puppet in that it needs to be a string that's unique throughout all of the resources on a given host's catalogue, we shouldn't always define an alias unless users really want them. This alias might (and did for some ppl) create a conflict when using a class that is named the same as $::hostname. We've just hit hit limitation on a Koumbit node. The alias attribute is legitimate in terms of nagios host attributes, but the name of the attribute clashes with the special-purpose attribute for puppet. So one might argue that the native puppet types are flawed, and they would be correct! but getting those types fixed would be a pain in the ass since they haven't been maintained for quite some time. See merge request !10
Diffstat (limited to 'files/pnp4nagios/pnp4nagios-templates.cfg')
0 files changed, 0 insertions, 0 deletions