New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #10362] Debian packaging: Separate package for CLI missing #2083
Comments
Updated by tgelf on 2015-10-14 15:51:08 +00:00
lazyfrosch, I found this: What's been the motivation for this change? Is there any related ticket? Thanks, |
Updated by mfrosch on 2015-10-20 08:06:47 +00:00
It currently makes no sense to ship a icingacli package, since the main application would be always required. It would makes sense if it can be a standalone installation. |
Updated by tgelf on 2015-10-20 18:17:55 +00:00
lazyfrosch wrote:
It absolutely makes sense, that's why packages where designed that way.
It can perfectly be installed standalone. And we want to do so. You can use icingacli on webless nodes just for check execution (e.g. icingacli businessprocess check ...). You can run a full-blown Icinga Web 2 server with no Apache and no Nginx while still offering the full web application. Modules can provide CLI tools in no way related to the web frontend, that's perfectly valid and strongly encouraged. IMHO it should be up to the project to decide what "makes sense" for a software project, that should not happen at distribution level. @lazyfrosch: please let me know whether it is possible to restore the former state or what concrete objections would hinder us from doing so. Thanks, |
Updated by elippmann on 2016-02-16 10:59:22 +00:00
I talked to Markus and he will take care that the CLI will be shipped as separate package. |
Updated by tgelf on 2016-02-16 11:21:56 +00:00
Hi Eric, I prefer to leave this open unless I see it solved ;) Cheers, |
Updated by elippmann on 2016-02-16 11:34:17 +00:00
|
Updated by mfrosch on 2016-02-22 12:11:59 +00:00
Done in > 2.1.2-2 and backports |
Updated by mfrosch on 2016-02-22 12:48:55 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10362
Created by tgelf on 2015-10-14 15:45:01 +00:00
Assignee: mfrosch
Status: Closed (closed on 2016-02-22 12:11:58 +00:00)
Target Version: 2.2.0
Last Update: 2016-02-22 12:48:55 +00:00 (in Redmine)
We used to have a "common", a "web" and a "cli" package for good reasons. I never tried out the Debian packages before - until now. Wanted to install icingacli and a custom module on a monitoring node. Web frontend is neither needed nor allowed on the target system.
Seems that the cli package has gone and icingacli is now part of "icingaweb2". And there is absolutely no way to install icingaweb2 without being bombed by an undesired full-blown web server. What happened here? At first sight, all other (not Debian based) distros look fine to me.
Regards,
Thomas
The text was updated successfully, but these errors were encountered: