The Lilac Network Configuration Platform

Going to add another export feature which will export the lilac database
(just the inserts, not the schema), which will give someone the ability to
reimport that sql dump into lilac. Exporting to configuration files then
re-importing will NOT bring things back into lilac the way they were
because lilac adds extra functionality to templates which nagios does not
understand. So, the need for sql snapshots is a must.

I didn't write the original bug report on that one, I just ported it from
the Fruity bugs because it looks fairly nasty. There have consistently been
a set of import and export inconsistencies, where doing an import and a
re-export reproduces fundamentally different configurations. I'm afraid to
say that I don't have a running Nagios/Lilac/Fruity setup right now, since
I just started a new contract (and hope Lilac will be usable for a Nagios
configuration there, but that's not on my tasklist yet!)

That whole set of spiraling inconsistencies can be reproduced by doing a
backup of the mysql database, exporting the Lilac, re-importing, backing up
the new database, re-exporting, and comparing the results. (You need the
backup to restore your original state!)

Is there any chance you can create a test case of configuration files and
provide them?