Optional construction of icinga2.debug directly in `icinga2 object list`

[tbauriedel]

With Icinga 2.14.0, icinga2.debug is not built by default with icinga2 daemon -C and thus also no longer built on reload or restart. This could lead to problems with some "custom" automatisms.

To bypass this extra step in automations, instead of executing the icinga2 daemon -C --dump-objects beforehand, it would be desirable to have an argument within the icinga2 object list that icinga2.debug creates in advance.

[Al2Klimov]

You mean an argument one had to pass explicitly, changing the existing automated process? What's the significant difference to executing icinga2 daemon -C --dump-objects beforehand?

[tbauriedel]

I know some Icinga 2 users who have automations based on icinga2 object list. In order for these automations to work with Icinga 2 2.14, an extra step to build icinga2.debug must be included. If there were an argument for icinga2 object list, one could save the extra step before and thus avoid errors. In automatisms, one might not see the message that the cache is outdated.

Additionally, I think it would improve the usability of icinga2 object list if you could build the cache directly there instead of having to do a icinga2 daemon -C --dump-objects every time before.
If you use icinga2 object list only once or rarely, building icinga2.debug beforehand is no big deal. In some cases, however, you will need the command several times in a row for debugging, checking etc. If changes occur in between, the extra step must be taken each time. After, say, the fifth time in a few minutes, this could get on the user's nerves.