Rudder 7.1 release notes

The list of currently available updates is now available as part of the inventory on most Linux systems (those using apt, yum/dnf or zypper).

It is exposed in the API and the Web interface, both in node details and in a new dedicated view, exposing additional information like update severity, description etc. when available.

Rudder 7.1 also comes with built-in techniques for full system update on Linux and Windows, allowing to schedule full system update campaigns. This feature will be improved in the following versions, with a dedicated interface.

Read the documentation for more information about this feature.

The Plugins sections disappears, and the plugins are now integrated into relevant categories.

We reworked the reporting engine to make reports easier to match to the policies part which produce them. This has been done by introducing a new unique identifier for each component. This allows:

This is completely transparent for the users.

The unique identifier has also been used to improve the agent-side reporting process, which has been refactored to be simpler, more reliable and to allow any re-execution of similar or identical methods. For now the following methods have been ported to the now report process:

Others will follow in upcoming versions.

A new method has been added, allowing to trigger an inventory at the next agent run. This allows updating the server side inventory more quickly after a change that impacts the inventory content (like package management, system upgrade, network changes, etc.)

The service methods can now be used with other systemd unit type by adding the extension (just like you would do on the CLI), like dnf-makecache.timer or tmp.mount.

This makes it easier to apply states on these units.

It is now possible, besides existing LDAP/AD authentication, to used OpenID Connect, enabling two factor authentication mechanisms and integration to your existing authentication providers.

Using our new design and tooling, we redesigned the page allowing the manage the API accounts. Apart from the visual improvements, it also improves the user experience with configuration popup for destructive actions (removal or replacement of a token) and hidden token with a button to copy the value, to avoid unwanted leak through screen sharing for example.

Several improvements were made to vulnerability management, especially on the memory usage.