feature request: icli compatibility for icinga2

[olaf7]

At the moment icli has hardcoded paths to Icinga datafiles. These can be overwritten by for example: icli -f /var/cache/icinga2/status.dat -c /var/cache/icinga2/objects.cache It would be nice if either these defaults would be configurable, be dynamically extracted from the Icinga configuration. An alterative would be to fork every release of icli to not only hold (in it's package) not only an icli executable which defaults to /var/cache/cinga/* but also an icli2 which defaults to /var/cache/icinga2/*

[derf]

They will be configurable in the next release (in git HEAD it already works). Also, I have patched Build.PL to check for both icinga1 and icinga2 paths -- So if you're building on a system with either of those installed and using the default paths, the build process should detect and use them automatically.

I'm considering adding support for an "icli2" symlink to icli, so that if it's called with icli2 it can use an appropriate set of default paths. That might be more convenient for packagers who want to support both icinga versions, but I'll have to think a bit about the implementation details.

[olaf7]

Good news! A symlink does sound like an easy solution which will cater for both icinga/icinga2

thank you,

Olaf On Thursday, May 15, 2014 5:04 PM, Daniel Friesel [email protected] wrote:

They will be configurable in the next release (in git HEAD it already works). Also, I have patched Build.PL to check for both icinga1 and icinga2 paths -- So if you're building on a system with either of those installed and using the default paths, the build process should detect and use them automatically. I'm considering adding support for an "icli2" symlink to icli, so that if it's called with icli2 it can use an appropriate set of default paths. That might be more convenient for packagers who want to support both icinga versions, but I'll have to think a bit about the implementation details. — Reply to this email directly or view it on GitHub.