20 Oct
2020
20 Oct
'20
11:52 a.m.
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 098e67253b291c0eedd590a557707262e8249f29
https://github.com/tribe29/checkmk/commit/098e67253b291c0eedd590a557707262e…
Author: Andreas Umbreit <andreas.umbreit(a)tribe29.com>
Date: 2020-10-20 (Tue, 20 Oct 2020)
Changed paths:
A .werks/11401
Log Message:
-----------
11401 New Bakery API
CMK-4680
Change-Id: I54a7210af45f51b82a5c3b653877386dcb673cd7
Commit: f78b5f7241291616e956fa67db25a5a996a33d1a
https://github.com/tribe29/checkmk/commit/f78b5f7241291616e956fa67db25a5a99…
Author: Andreas Umbreit <andreas.umbreit(a)tribe29.com>
Date: 2020-10-20 (Tue, 20 Oct 2020)
Changed paths:
A .werks/11402
Log Message:
-----------
11402 Agent Bakery: New "Bake and sign" action
It is now possible to bake and sign all agents in one step. You can simply do this by
pressing
the corresponding button at the agent bakery. It will be available as soon as at least
one
signature key has been created or imported.
When invoking "Bake and sign agents", you will be prompted for selecting a
signature key and
entering its passphrase. After that, every agent package will get baked and signed
immediately
after baking.
When using "Bake and sign", it is assured that there are no unsigned packages
visible for
download at any time, avoiding that it could be seen accidentally by a calling agent
updater,
leading to a "The deployment server provides an agent but that is not signed."
error.
The "Bake and sign" action is also available via REST API, please refer to the
documentation
for details.
CMK-4680
Change-Id: I47706ea843b1c7f0e53561d6e7e5d87ea39d2930
Commit: 5cae433d3c160d315f2a3ce4e90daaf9a4e8ed90
https://github.com/tribe29/checkmk/commit/5cae433d3c160d315f2a3ce4e90daaf9a…
Author: Andreas Umbreit <andreas.umbreit(a)tribe29.com>
Date: 2020-10-20 (Tue, 20 Oct 2020)
Changed paths:
A .werks/11403
Log Message:
-----------
11403 Improved versioning for baked agent packages
Previously, when updating a baked agent via a package manager, you would eventually
receive a warning about a downgrade of the Checkmk agent. The reason for this was the
baked agent's version string, that was formed of Checkmk version and the agent's
configuration
hash , with the latter being quite random and thus confusing the package manager, that
expects
an increasing versioning. E.g. a version string could be
<tt>1.6.0p18.f123abcd</tt> before bake,
and <tt>1.6.0p18.1234cdef</tt> after bake.
This behavior is now fixed by introducing an internal bake revision, that increases on
every
newly baked package (per Checkmk version) and that's only purpose is to guarantee an
inceasing version string for the .rpm, .deb and .pkg packages (e.g.
<tt>1.6.0p18-1.f123abcd</tt>
before bake, <tt>1.6.0p17-2.1234cdef</tt> after bake). Please note that this
revision won't
be visible on the GUI or in the package's filenames, it only affects the package's
metadata.
CMK-4860
Change-Id: I5d2c65de22bc64ebb1cb53f76d6a77082428658f
Compare: https://github.com/tribe29/checkmk/compare/42310d92d6b5...5cae433d3c16