Project

General

Profile

Actions
Copy link

Bug #15024

closed

It should be forbidden to create a user technique with the same name as n existing technique

Bug #15024: It should be forbidden to create a user technique with the same name as n existing technique

Added by Benoît PECCATTE over 6 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Elaad FURREEDAN
Category:
Web - Technique editor
Target version:
6.1.5
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
82
Name check:
Fix check:
Checked
Regression:

Description

It is currently possible to create a custom technique with the technique editor with the same id as a package provided technique.
There is then a conflict and we cannot see the new technique.
This should be forbidden in the technique editor / the api

Subtasks 1 (0 open — 1 closed)

Bug #18277: Bad condition on name checking for technique existenceReleasedFrançois ARMANDActions

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #18098: Alert user if they named a technique with a name that already exists in provided techniquesReleasedElaad FURREEDANActions

Updated by Alexis Mousset over 6 years ago Actions
Copy link
 #1

  • Category set to Web - Technique editor

Updated by François ARMAND about 6 years ago Actions
Copy link
 #2

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Effort required set to Small
  • Priority changed from 0 to 80

Is it still the case in 6.0 ?

Updated by François ARMAND over 5 years ago Actions
Copy link
 #3

  • Assignee set to Elaad FURREEDAN
  • Target version set to 6.1.2
  • Effort required changed from Small to Very Small
  • Priority changed from 80 to 82

Still the cas in 6.1 and give really strange results if id exists but not version.

I propose to change it only in 6.1 since internal API totaly changed in that version (before: call to python, etc. Now: internal rudder api).

Updated by Elaad FURREEDAN over 5 years ago Actions
Copy link
 #5

  • Status changed from New to In progress

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #6

  • Target version changed from 6.1.2 to 6.1.3

Updated by François ARMAND over 5 years ago Actions
Copy link
 #7

  • Target version changed from 6.1.3 to 6.1.4

Updated by Elaad FURREEDAN over 5 years ago Actions
Copy link
 #8

  • Pull Request set to https://github.com/Normation/rudder/pull/3163

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #9

  • Target version changed from 6.1.4 to 6.1.5

Updated by Anonymous over 5 years ago Actions
Copy link
 #10

  • Status changed from In progress to Pending release

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #11

  • Fix check set to To do

Updated by François ARMAND over 5 years ago Actions
Copy link
 #12

  • Fix check changed from To do to Checked

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #13

This bug has been fixed in Rudder 6.1.5 which was released today.

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #14

  • Related to Bug #18098: Alert user if they named a technique with a name that already exists in provided techniques added

Updated by Vincent MEMBRÉ over 5 years ago Actions
Copy link
 #15

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: PDF Atom