Bug #14330
closed
By default, no group are supervised and new group are not supervised
Added by François ARMAND almost 6 years ago.
Updated over 1 year ago.
Category:
Web - Config management
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I hate Rudder for that
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Description
When we install the change validation plugin no groups are selected as supervised so all modification are accepted without any change request.
Moreover, a new group is created as unsupervised which is a major authorization management problem.
By default, all groups and futur new group must be supervised, making them unsupervised must be a willing action.
To make that change without breaking compat, we need to store the "unsupervised-groups" and add a migration from the "supervised-groups" to unsupervised.
- Project changed from Change validation to Rudder
- Target version deleted (
5.0-1.3)
- Related to User story #14333: Remote run should optionnaly honor splay time in async mode added
- Related to deleted (User story #14333: Remote run should optionnaly honor splay time in async mode)
- Category set to Web - Config management
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 32
- Target version set to 5.0.13
- Priority changed from 32 to 31
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 31 to 30
- Target version changed from 5.0.14 to 5.0.15
- Priority changed from 30 to 29
- Effort required set to Very Small
- Priority changed from 29 to 54
- Target version changed from 5.0.15 to 5.0.16
- Priority changed from 54 to 53
- Target version changed from 5.0.16 to 5.0.17
- Priority changed from 53 to 51
- Target version changed from 5.0.17 to 5.0.18
- Target version changed from 5.0.18 to 5.0.19
- Target version changed from 5.0.19 to 5.0.20
- Target version changed from 5.0.20 to 797
- Target version changed from 797 to 6.1.14
- Target version changed from 6.1.14 to 6.1.15
- Target version changed from 6.1.15 to 6.1.16
- Target version changed from 6.1.16 to 6.1.17
- Target version changed from 6.1.17 to 6.1.18
- Target version changed from 6.1.18 to 6.1.19
- Target version changed from 6.1.19 to 6.1.20
- Priority changed from 51 to 52
- Target version changed from 6.1.20 to 6.1.21
- Priority changed from 52 to 53
- Target version changed from 6.1.21 to old 6.1 issues to relocate
- Subject changed from By default, no group is selected => it seems that change requests don't work to By default, no group are supervised and new group are not supervised
- Description updated (diff)
- Target version changed from old 6.1 issues to relocate to old 6.2 issues to relocate
- Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
- UX impact set to I hate Rudder for that
- Effort required changed from Very Small to Small
- Priority changed from 53 to 137
- Regression set to No
- Status changed from New to In progress
- Assignee set to François ARMAND
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder-plugins/pull/547
- Status changed from Pending technical review to Pending release
- Priority changed from 137 to 138
- Status changed from Pending release to Released
- Priority changed from 138 to 139
This bug has been fixed in Rudder plugin change-validation v7.3.1-2.1
This bug has been fixed in Rudder plugin change-validation v7.2.6-2.1
Also available in: Atom
PDF