Actions
Bug #20734
closed
Duplicate classes RudderUserDetails
Status:
Released
Priority:
N/A
Assignee:
Category:
Architecture - Internal libs
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
During a refactoring, we duplicated (in place of moving) RudderUserDetails and CurrentUser.
This can lead to really suprising behaviour, and it's a suprise nothing broke.
Old RudderUserDetails does not seem to be used in plugins.
Unfortunatly, CurrentUser (the incorrect one) is used in ChangeValidation, so we will need to keep a stub for compat if we want to do it in 6.2.
For that, I propose to do the change in 7.0 only and only backport if an user-visible problem is discovered because of that.
Updated by François ARMAND about 2 years ago
- Status changed from New to In progress
Updated by François ARMAND about 2 years ago
- 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/pull/4162
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.0.1 to 7.0.2
Updated by François ARMAND about 2 years ago
- Target version changed from 7.0.2 to 6.2.13
We decided to target 6.2 branch for that ticket that is needed for oauth plugin
Updated by François ARMAND about 2 years ago
- Related to Bug #20735: Counterpart of 20734: update import for RudderUserDetails added
Updated by François ARMAND about 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|e001cf369db005fccd43edcb2c2702f8ac62114e.
Updated by François ARMAND about 2 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.2.13, 7.0.2 and 7.1.0~rc1 which were released today.
Actions