Rudder 7.2 release notes

The patch management feature gains the ability to schedule upgrade campaigns across your nodes.

You can define either one-shot or recurring (weekly or monthly) campaigns, targeting a set of groups. You also define a time windows, and the upgrades will automatically be spread across the target nodes.

Once the upgrade has run, you get a centralized view over the results.

And you can also access detailed logs to troubleshoot any issue.

It is now possible to export to and import from another server a rule or directive and all of its dependencies (including techniques from the technique editor).

This allows finer-grained synchronization compared to git repository synchronization.

Reporting will now be correct when using iterator variables as input for methods (for example when using an iterator variable to install several packages).

We renamed the agent types to make them clearer for users:

The plugin "create-node" allowed pre-creating nodes in Rudder. This means making the node visible in the interface, and being able to pre-provision settings (certificate, node properties, etc.) before the node actually sent its first inventory. This is useful in a provisioning automation context.

This feature is now part of the base HTTP API.

We added support both as server and agent for RHEL 9 and derivatives (CentOS Stream, Rocky Linux, AlmaLinux, Oracle Linux).

This allows matching the behavior of authentication sources (en particularly Active Directory).

It is not a lot easier to make changes to the Rudder server configuration by deploying them as overrides over the default configuration in the rudder-web.properties.d (with a the .conf extension).

We added a page in the settings section to show the list of currently configured server hooks.

Notable performance improvements were made to the vulnerability tracking feature.

A small cosmetic update was made on the dashboard to better match the new style.