Include customizations of the plugin files into the agent hash

4 votes

The main reason for this request is the need to re-roll all agents after you changed a plugin or config file, but the agent bakery doesn't realize, that there are new changes.

I wished, that the custom plugins and local-script, which will be deployed over the check_mk site via "Deploy custom files with agent" and other self-made rules, are also counted into the agent hash.
That way, even small change in the files will lead to a new agent to be rolled-out.

ATM, it's not possible to "force" a new deployment from Check_MK-site, without the need, to change rules. In my case, i made a dummy rule, which does nothing, but that way the agent hash will be changed.

Under consideration Agent Bakery Suggested by: Kruzgoth (04 May, '23) • Upvoted: 03 Nov, '23 • Comments: 2

Comments: 2

05 May, '23
JPH
Kruzgoth thanks for that information!
This is the base of the deployment and the detection of the agent deployment. Why is this not implemented yet?
Now I know the problem why our agents not baked and deployed and we chaged rule by rule that the agent will be baked again.
I higly reccoment the implementation!
15 May, '23
AndiU
One part of your request is already implemented since Checkmk 2.0:

"I wished, that the custom plugins and local-script, which will be deployed over the check_mk site via "Deploy custom files with agent" and other self-made rules, are also counted into the agent hash.
That way, even small change in the files will lead to a new agent to be rolled-out."

See https://checkmk.com/werk/11404
If this doesn't work, it would rather be a bug than a feature request :)

However, the agent bakery won't detect changes in bakery plugins (in contrast to agent plugins), as this is, technically spoken, not something that gets packaged, but rather code that is executed by the bakery.

Instead of trying to catch all possibilities that can result in new packages, would it be feasible to be able to actually enforce new hashes for every package?