The Director aims to be your new favourite Icinga config deployment tool. Director is designed for those who want to automate their configuration deployment and those who want to grant their “point & click” users easy access to the configuration.
Hello, I'm considering starting using the Import and Sync features of the Director but I'm a bit concerned that it may one day accidentally purge the rest of the hosts already added in the Director.
I've confirmed in the testing environment that the "Purge" option in the Sync settings currently only applies to the hosts imported from the Import Source but I would like to understand the mechanism better.
Can anybody please explain to me how the imported objects are being tracked and if there are any caveats I should be aware of before implementing it in my environment?
Hello, I'm considering starting using the Import and Sync features of the Director but I'm a bit concerned that it may one day accidentally purge the rest of the hosts already added in the Director.
I've confirmed in the testing environment that the "Purge" option in the Sync settings currently only applies to the hosts imported from the Import Source but I would like to understand the mechanism better.
Can anybody please explain to me how the imported objects are being tracked and if there are any caveats I should be aware of before implementing it in my environment?