Rudder

I'm marking it blocking, because we need to know before 4.3-finale if there is something missing in the pre/post facility and correct it now.

• add a tag to the bundles of the Directives
• in pre-hooks, find all these bundle with tags, get all the users/flush, and for all user that have at least a flush, create an empty file .tmp (or .rudder) for the sshkey, and for the other copy the existing authorizedkey to this .rudder (or .tmp) file
• in the directive, edit the .tmp or .rudder file
• in the post-hook, for the flushed file, if .tmp is different that the sshkey file, report repaired for all the keys of this user, and for those non-flush, base the reporting on the classes defined in the directive itself

This is a non-trivial implementation, but it allows for use case that are broken at the moment, and seems the easiest way to deal with the directive by directive

PR https://github.com/Normation/rudder-techniques/pull/1339

Applied in changeset rudder-techniques|c85e0c69621127efcd5600efb8ff38152014ffbe.

• Download: https://www.rudder-project.org/site/get-rudder/downloads/

Changelog
 Changelog