Rudder

Nicolas CHARLES wrote:

Matthieu, I've made some comments on the techniques
Except for the reporting issue, they look great (with awesome use of dependencies)
However, the Master needs to be used in conjonction with any of the others; i'm not sure it is the intended scenario within Rudder, and it could lead to unexpected error

Thanks Nicolas.

That's a good point, currently AutoFSMountPoint will fail in mysterious ways if master is not also used. I shall fix that :)

The AutoFSUnmanagedMap won't fail, it just won't do anything without a master.

There are dependencies between them, and master needs to be applied for anything to actually be changed, but it's the best way I could come up with that allows the flexibility of defining multiple mounts, possibly across multiple directives, and having them aggregated on a host, and also allowing to define maps that are not managed by rudder so that local admins may fiddle with them as they please :)

I closed the PR https://github.com/Normation/rudder-techniques/pull/62 because it was targetting Rudder 2.4

A new implementation of that Technique can take inspiration from that PR nonetheless.