Project

General

Profile

Actions
Copy link

Bug #3782

closed

Rename a Technique in the git repository lead the Directives associated to be lost and the Rules to be in error

Added by Nicolas PERRON over 11 years ago. Updated about 11 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Config management
Target version:
2.4.9
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When a rename of a Technique is needed, we have to do it into the git repository of Rudder but after this have been done, the Directives related to this Techniques are lost and the Rules related to these Directives are in Error.

Actions
Copy link
 #1

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.7 to 2.4.8
Actions
Copy link
 #2

Updated by François ARMAND about 11 years ago

  • Status changed from New to Discussion
  • Assignee set to Nicolas PERRON

By renaming a technique, do you mean changing it's file name ? Or changing the value of <TECHNIQUE name="XXXX"> in the metadata.xml file ?

Actions
Copy link
 #3

Updated by Nicolas PERRON about 11 years ago

  • Assignee changed from Nicolas PERRON to François ARMAND

François ARMAND wrote:

By renaming a technique, do you mean changing it's file name ? Or changing the value of <TECHNIQUE name="XXXX"> in the metadata.xml file ?

I'm not sure about only the rename of <TECHNIQUE name="XXX"> but renaming all (and then, "moving" the directory), the Rule will be in error instead of just skipping the not functionnal Directive.

Actions
Copy link
 #4

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.8 to 2.4.9
Actions
Copy link
 #5

Updated by François ARMAND about 11 years ago

  • Assignee changed from François ARMAND to Nicolas PERRON

That is the expected behavior, because we don't want to silently have rule whose directive are no more here, we want it to be very visible.

For example, if we have a "Base security for the company" technique, we certainly don't want that rule having it continu to work has nothing happened if someone deleted the technique.

Actions
Copy link
 #6

Updated by Nicolas PERRON about 11 years ago

  • Assignee changed from Nicolas PERRON to François ARMAND

François ARMAND wrote:

That is the expected behavior, because we don't want to silently have rule whose directive are no more here, we want it to be very visible.

For example, if we have a "Base security for the company" technique, we certainly don't want that rule having it continu to work has nothing happened if someone deleted the technique.

Ok, seems logic. The name of the Technique should be modified into the metadata.xml file, not onthe filesystem...

I've tested to rename into metadata.xml and the behavior seems logic:
  • The name displayed into Rudde WebUI is the name from the latest version of the Technique.
  • In the details of a Directive, the name correspond to the name of the Version its Technique.

I suppose then we can reject this bug. Do you agree ?

Actions
Copy link
 #7

Updated by François ARMAND about 11 years ago

  • Status changed from Discussion to Rejected

Yep, rejected!

Actions
Copy link

Also available in: Atom PDF