Architecture #20747
closedUse a unique id to identify reports
Description
We use to match report by looking to their component value and their values. but this leads to various falws in our compliance computation system.
We don't match reports precisely and we have to group all reports that have the same component so we cannot be sure that the report we correctly assigned, espcially in case where we have varialbe
It does not mix well with block feature, since we cannot find out from the report in which block this report belong (if the component name is shared with others)
We can not use varialble in component name, and it something we really want to do.
Updated by Vincent MEMBRÉ over 2 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ over 2 years ago
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/4167
Updated by Vincent MEMBRÉ over 2 years ago
- Status changed from In progress to Pending release
Applied in changeset rudder|15ad1429e6a66ed54202a51516355af706de464c.
Updated by François ARMAND over 2 years ago
- Pull Request changed from https://github.com/Normation/rudder/pull/4167 to https://github.com/Normation/rudder/pull/4184
Updated by Vincent MEMBRÉ over 2 years ago
Applied in changeset rudder|358937df1422bca047ac9cfd5c939928e05c31c4.
Updated by Alexis Mousset over 2 years ago
Applied in changeset rudder|9dbdd039d005f3de095691fff879103e6c082a7e.
Updated by Vincent MEMBRÉ over 2 years ago
This bug has been fixed in Rudder 7.1.0~beta1 which was released today.
Updated by Alexis Mousset about 2 years ago
- Status changed from Pending release to Released