Werk #16076: Agent Bakery: "Bake revision" is now configurable
| Component | Agent bakery | ||||||||
| Title | Agent Bakery: "Bake revision" is now configurable | ||||||||
| Date | Aug 7, 2023 | ||||||||
| Level | Trivial Change | ||||||||
| Class | New Feature | ||||||||
| Compatibility | Incompatible - Manual interaction might be required | ||||||||
| Checkmk versions & editions |
|
This Werk is incompatible only for Checkmk 2.3, while the default behavior won't change for Checkmk 2.2 and lower.
With Checkmk 2.0/Werk #11403 we introduced a new versioning scheme for
baked agents that includes a so-called "Bake revision".
However, the big downside of this approach is that agents will lose their
signature in many cases when baking new agents without signing.
With this Werk, it's possible to deactivate/activate the bake revision by configuring the global setting Setup/Apply bake revision.
Additionally, when agents are baked automatically due to an active
Setup/Automatically create monitoring agents setting, starting with Checkmk 2.3,
the bake revision won't increase.
By this, we avoid a situation where agent signatures are invalidated automatically.
Breaking change: Due to the feedback of many users, the default behavior will
change with Checkmk 2.3: The bake revision will be deactivated by default.
If you happen to rely on the versioning scheme mentioned in Werk #11403, you have to
re-activate the bake revision manually.
For Checkmk up to 2.2, the bake revision will remain activated by default.
Breaking change: As mentioned above, also starting with Checkmk 2.3, the bake
revision (when activated at all) won't increase when agents are baked automatically on
activate changes.
If your workflow relies on a versioning scheme with bake revision and on automatic
baking, you have to switch to a different approach, e.g., bake agents regularly via REST-API.