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 8 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 #1

Updated by Nicolas CHARLES over 11 years ago

Hum,

That's a tricky point. We can't prevent user from applying directives editing the same file, unless we want to embeed a lot of information in the metadata (like we can edit to add line twice, but can edit completely the file twice, or can edit completely and add line)

But we could have something that warn the user if directives touch the same component several times, so that the user can review what's going on; would that help ?

Actions #2

Updated by Benoît PECCATTE almost 10 years ago

  • Project changed from 30 to Rudder
  • Category set to Documentation
Actions #3

Updated by Benoît PECCATTE over 8 years ago

  • Target version set to 2.11.21
Actions #4

Updated by Alexis Mousset over 8 years ago

  • Category changed from Documentation to Web - Config management
Actions #5

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #6

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #7

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #8

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.24 to 308
Actions #9

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 308 to 3.1.14
Actions #10

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #11

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #12

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #13

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #14

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #15

Updated by Benoît PECCATTE almost 8 years ago

  • Tracker changed from Bug to User story
  • Subject changed from same file edited by 2 different directives to Forbid same file edited by 2 different directives
Actions #16

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #17

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #18

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #19

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #20

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #21

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #22

Updated by Benoît PECCATTE about 7 years ago

  • Target version changed from 3.1.25 to 4.1.9
Actions #23

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions #24

Updated by Benoît PECCATTE almost 7 years ago

  • Target version changed from 4.1.10 to Ideas (not version specific)
Actions #25

Updated by François ARMAND 8 months ago

  • Status changed from New to Rejected
  • Regression set to No

We won't support that any time ahead. The general direction would be to use dedicated rudder module that manage update on some files and check by themself that they remind consistent.

I'm closing it since we won't provide it without a clear use case, and perhaps sponsoring.

Actions

Also available in: Atom PDF