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 over 5 years ago.
Updated about 4 years ago.
Category:
Web - Technique editor
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
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
- Category set to Web - Technique editor
- 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 ?
- 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).
- Status changed from New to In progress
- Target version changed from 6.1.2 to 6.1.3
- Target version changed from 6.1.3 to 6.1.4
- Pull Request set to https://github.com/Normation/rudder/pull/3163
- Target version changed from 6.1.4 to 6.1.5
- Status changed from In progress to Pending release
- Fix check changed from To do to Checked
This bug has been fixed in Rudder 6.1.5 which was released today.
- Related to Bug #18098: Alert user if they named a technique with a name that already exists in provided techniques added
- Status changed from Pending release to Released
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Anonymous