Project

General

Profile

Actions

User story #3614

closed

Forbid same file edited by 2 different directives

Added by Fabrice FLORE-THÉBAULT over 11 years ago. Updated 7 months ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
No

Description

Let's have a directive called foo, which will edit the full content of the file /tmp/twins as such:

foo
yeah
foo

Let's have a directive called bar, which will edit the full content of the file /tmp/twins as such:

bar
barbar

Let's apply both directives to the same host.

This is impossible, they are in conflict, right.

What should happen?

We certainly would like to be notified by Rudder Server that it will be impossible to apply those directives, because there is some conflict between 2 directives named foo and bar.
Even better: the Rules regenaration should NOT be done, as the result can be unexpected.

What should the file look like at the end ? I don't know.

Apparently, cfengine chooses to resolve the conflict by merging the 2 files, so you will get something like:

foo
yeah
foo
bar
barbar
Actions

Also available in: Atom PDF