Yonas Habteab
Yonas Habteab
Actually it does have a way and that is the following `${@:1}`, however, as we are using `sh` shebang for whatever reason, this syntax is invalid.
**Test** cases for https://github.com/Icinga/icinga2/issues/7398 Config ``` object TimePeriod "24x7" { ranges = { wednesday = "00:00-23:59" } } object TimePeriod "offDuty" { ranges = { wednesday = "10:00-17:00" } }...
Running tests for https://github.com/Icinga/icinga2/issues/8741: http://10.27.0.228/icingaweb2/dashboard
> * creation of such objects with the given attributes via the API What does the `no_user_modify` flag actually have to do with creating a new object? It is only...
> Please update the PR description to specify the config that was used in each case and clearly state when a process did not terminate when it should or when...
> Please also share the config you used for your performance test. Config ```bash object CheckCommand "dummy" { import "dummy-check-command" vars.dummy_state = 0 vars.dummy_text = "Check was successful." } template...
Actually it doesn't look so inferior, but four out of a total of 6 arguments of the current plugin would not work with this alternative. 1. `elasticsearch_failuredomain`, `elasticsearch_masternodes` and `elasticsearch_prefix`...
https://www.claudiokuenzler.com/monitoring-plugins/check_es_system.php This would be also a good alternative and is up-to date with much more options than what we are already using. But since I don't ever/use Elasticsearch, I can't...
> If `ignore_on_error` crashes API objects, how did regular config objects ever work? As I already said, the problem appears only after this fix. > You can only reproduce the...