Rudder

Yes, this is due to a limitation in how we write techniques and how cfengine convergence works.

To make sure a technique is update-safe, we are thinking at how to solve this but it needs long term changes.

To work around the limitations, the best thing is to use templates.

We should have an edit zone for rudder, and cleanly managed everything in that zone.

Nicolas CHARLES wrote:

We should use file_ensure_block_in_section to create and edit section

Actually, this would prevent detecting which command has been edited
So we could either create a new generic method that would have name of section as class parameter, or find another solution :/

To have a correct fix with generic method, we need to have composite keys for reporting, and this is quite a big change (it could only be in master for ncf), even if located only in ncf
So to have a suitable fix in Rudder 3.1, we'll create an ad-hoc code, like a generic method, in sudo technique, to edit section with proper reporting

there a huge question mark here.
We are moving from managing file like

# User privilege specification
root    ALL=(ALL:ALL) ALL

%admin ALL=(ALL) ALL

%sudo    ALL=(ALL:ALL) ALL

to

# User privilege specification
root    ALL=(ALL:ALL) ALL

# Configuration name Name 1
%admin ALL=(ALL) ALL
# End Configuration name Name 1

# Configuration name Name 2
%sudo    ALL=(ALL:ALL) ALL
# End Configuration name Name 2

#Managed by Rudder

#End of section Managed by Rudder

Work in progess here: https://github.com/ncharles/rudder-techniques/commit/cc6cb63270bdaf37a6ee0bd7c77ccedae081b7b6

Work in progess here: https://github.com/ncharles/rudder-techniques/commit/6235842da742c2d26b3b3a6dc5e1a036b050c050

Decided solution:
we check if expected line is there - if it is, but not in the section (and the section doesn't exist somewhere else), we wrap it around the section.
Otherwise, if section is there, we edit it
otherwise, we add the section