Project

General

Profile

Actions

Bug #15024

closed

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

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

Status:
Released
Priority:
N/A
Category:
Web - Technique editor
Target version:
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 open1 closed)

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

Related issues 1 (0 open1 closed)

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

Updated by Alexis Mousset almost 5 years ago

  • Category set to Web - Technique editor
Actions #2

Updated by François ARMAND over 4 years ago

  • 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 ?

Actions #3

Updated by François ARMAND almost 4 years ago

  • 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).

Actions #5

Updated by Elaad FURREEDAN almost 4 years ago

  • Status changed from New to In progress
Actions #6

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.2 to 6.1.3
Actions #7

Updated by François ARMAND over 3 years ago

  • Target version changed from 6.1.3 to 6.1.4
Actions #8

Updated by Elaad FURREEDAN over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.4 to 6.1.5
Actions #10

Updated by Anonymous over 3 years ago

  • Status changed from In progress to Pending release
Actions #11

Updated by Vincent MEMBRÉ over 3 years ago

  • Fix check set to To do
Actions #12

Updated by François ARMAND over 3 years ago

  • Fix check changed from To do to Checked
Actions #13

Updated by Vincent MEMBRÉ over 3 years ago

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

Actions #14

Updated by Vincent MEMBRÉ over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF