> > In other words, if the desired way to do configuration is to have an > intelligent config > generator that produces stupid service/host definitions without templating, > etc. > all the above is obsolete. > > So, that's it for now. > What do you think? What's the focus of the dev-team? > > Matthias
This is the direction I am going (if I understand you correctly), in that a REST API will be the only entry point in/out of the server, and will just take commands like addHost, updateHost, updateService, etc. Once Andreas gets the hot add/remove functionality he’s talked about this would be really slick since then if you’re writing out the configs whenever there is a change, it will always be in sync and no more worry about the config mistakes. I think the current flat config file syntax is too old and not flexible enough. I would love to be able to do things like define new types, why only host and services, why not just call them whatever you want, like I want to define “applications” and assign whatever properties I want to them. Then the config files could just be like “expansion pack’s” that have new definitions, so a specifc firewall type might have special definitions for it, or the other thing it would help with is being able to dump data from a CMDB since you could make the fields line up right. Dan
