Am 09.07.2016 um 01:15 schrieb Michael Martinez:
On Thu, Jun 30, 2016 at 7:36 AM, Joosten, Markus
<markus.joos...@plumbe.de> wrote:
Do you have the icinga2 feature "api" enabled on your system?
Yes I do. Is there an api command to extract the config file?
In any case, I was able to restore the file by grepping through the
hard drive partition for a character string that I knew was in the
file. So, problem averted. And then promptly created a git repo to
hold all the config files. ... And then a salt state to keep it up to
date on the server ... etc
In any case, I still am interested to know if one can extract or
reconstruct the config files with relative ease by probing Icinga.
Config files do not exist anymore when querying it from memory. The
config files are parsed, compiled and committed into memory. In the end
you'll have a fully compiled object with all attributes - be it
inherited from templates, or even generated from apply rules.
Git is a good choice for your workflow. That's also something we try to
encourage in our trainings - use existing tools and work with their
capabilities. Branches, Diffs, etc. - in case you're using Puppet you'll
certainly know that from r10k already somehow.
Kind regards,
Michael
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
--
Michael Friedrich, DI (FH)
Senior Developer
NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
Tel: +49 911 92885-0 | Fax: +49 911 92885-77
CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
http://www.netways.de | michael.friedr...@netways.de
** OSBConf 2016 - September - osbconf.org **
** OSMC 2016 - November - netways.de/osmc **
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
