Actions
Bug #5484
closedDo not accept technique with same name
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
We only check that bundle_name is different, but we should also prevent creating a technique with the same name
create technique a (bundle name a)
create technique b (bundle name b)
rename b to a (bundle name still b)
Two techniques a => CONFUSING
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from New to Pending technical review
- Pull Request set to https://github.com/Normation/ncf/pull/157
Updated by Vincent MEMBRÉ about 10 years ago
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Target version set to 0.x
- Pull Request changed from https://github.com/Normation/ncf/pull/157 to https://github.com/Normation/ncf/pull/158
PR here :https://github.com/Normation/ncf/pull/158
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 75ed5b9a42af7489891556a87c05bddc0f0c8a55.
Updated by François ARMAND about 10 years ago
Applied in changeset 45829bbf4a20e316eab9dbf4bb45feb56408f6c6.
Updated by Vincent MEMBRÉ over 8 years ago
- Status changed from Pending release to Released
Updated by Alexis Mousset over 2 years ago
- Target version changed from 0.x to ncf-0.x
- Priority set to 0
Updated by Alexis Mousset over 2 years ago
- Project changed from 41 to Rudder
- Category set to Generic methods
Actions