Have a look at the previous version for our initial motivation.
Fortunately, we had the possibility to work together with Icinga to integrate most of our changes into the master branch of the official Icinga Director. However, we are still missing one feature that we need for our deployments: Automatic renaming of applied custom variables.
This version of our fork:
- is based on the official master branch (commit 35e90f7b6008075bb6d61a55fe12988df3c8b5c7)
- automatically renames applied related vars during basket imports. Have a look at Testing for details.
- fixes Icinga#2725
- fixes Icinga#2734
- makes the MySQL migrations "nicer" - they do not fail if the uuid columns already exist (making migrations easier)
Follow the installation instructions.
Migrating from Linuxfabrik fork v1.8.1 or lower:
- Important: Disable the Director module in IcingaWeb2 before installing this fork.
- Install this fork.
- Apply the required SQL migrations:
mysql -p -u root icinga_director < schema/guids2uuids-migration.sql- Enable the Director.
Migrating from v1.10.2+ or Linuxfabrik fork v1.10.2.2023020901:
- Install this fork.
- Use DB-Migrations offered in IcingaWeb2.
- Since the fork is based on the master branch instead of a full release, there are still some open upstream bugs to be expected.
- DataFields: Renaming or removing an entry will only rename/remove the entry in the datalist, not the applied variables on other objects such as hosts or services.
- The fork is not tested with Configuration Branches for Icinga Director.
- Import rename-related-vars1.json
- Create a host which has the custom variable applied and contains a value:
icingacli director host create host1 --imports ___TEST___host_template1 --vars.___TEST___datafield1 'myvalue1' - Import rename-related-vars2.json
- During this import the variable was renamed from
___TEST___datafield1to___TEST___datafield1-renamed. - Make sure that the applied variable on the host is also renamed:
icingacli director host show host1