20 Oct
2020
20 Oct
'20
1:32 p.m.
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 2eac736889de1151f9b05ae6fd3c2c16e9543095
https://github.com/tribe29/checkmk/commit/2eac736889de1151f9b05ae6fd3c2c16e…
Author: Andreas Umbreit <andreas.umbreit(a)tribe29.com>
Date: 2020-10-20 (Tue, 20 Oct 2020)
Changed paths:
A .werks/11404
Log Message:
-----------
11404 Better detection of changes in baked agent packages
Previously, the only property that has been observed by the agent bakery to decide
whether
to bake new agents, was the WATO agent configuration. This sometimes lead to problems
when
deploying your own plugins, because changes in agent plugin files won't get recognized
and
hence no new agent would get baked. Furthermore, if you managed to force-bake the agents,
including the file changes, the config hash would still stay the same, hence the agent
updater
would refuse to deploy the new package to the hosts.
The agent bakery will now recognize changes in every file that gets deployed to the
configured
agent packages and reflect them in generating a different agent hash on baking agents.
Similar
to a config change, changes in underlying files will lead to a highlighted "Bake
agents" button
at the agent bakery.
Please note that this mechanism will only work work bakery plugins that are specified via
the new Bakery API, see Werk #11401. This includes all builtin bakery plugins. E.g., if
you
decide to adapt the Checkmk linux agent (copy an adapted version to the local hierarchy),
your changes will get recognized.
CMK-4860
Change-Id: Iccd1ed937bde2439bad4b5e3c5352e8895a30935