Skip to content
This repository has been archived by the owner on Oct 12, 2019. It is now read-only.

Remove configuration validity checking from role #9

Open
goetzk opened this issue Mar 21, 2017 · 1 comment
Open

Remove configuration validity checking from role #9

goetzk opened this issue Mar 21, 2017 · 1 comment
Labels
enhancement

Comments

@goetzk
Copy link
Owner

goetzk commented Mar 21, 2017 •
edited
Loading

As mentioned in issue #8 , validity checking in the templates is painful. this should be removed and left to a validation command before doing the restarts.
goetzk added a commit that referenced this issue Apr 11, 2017
@goetzk
Start of contact groups for issue #5
b69cd34 
Contact groups are a useful way of sending alerts and avoiding single person
failures. I can't quite figure out what I need to do yet so I'm goint to put
this on the backburner while I consider issues #7 and #9.
goetzk added a commit that referenced this issue Apr 16, 2017
@goetzk
Start of work on issue #9
be159e0 
This is the bulk of the in built validity checking. The items which remain are
things I want to test further before changing which means they won't be
modified for the moment.
@goetzk
Copy link
Owner Author

goetzk commented Apr 16, 2017

templates/hosts.cfg.tmpl and templates/services.cfg.tmpl are the only templates with special casing now. The special casing in those files may not be optional as it handles the host groups. I'll need to do some separate testing on that to find out if i can remove it or not.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@goetzk