Actions
User story #25600
closedUser story #25383: Worst report takes the worst component instead of block
Compliance reporting with type worst-case-percent is not known by rudderc
Pull Request:
UX impact:
I dislike using that feature
Suggestion strength:
User visibility:
Effort required:
Small
Name check:
To do
Fix check:
To do
Regression:
No
Description
When implementing the parent ticket, we need the rudderc compiler for techniques to known about this new value, especially since we removed the fallback to webapp compiler in #25504. We have the following compilation error when attempting to save techniques with the new report type :
WARN techniques.writer.rudderc - -> stderr : ERROR | - id: 4fab048e-57d2-45df-b73a-1f9c98437821 | name: my block | reporting: 9 | mode: worst-case-percent | ^ items[0].reporting.mode: unknown variant `worst-case-percent`, expected one of `worst-case-weighted-sum`, `worst-case-weighted-one`, `focus`, `weighted`, `disabled` at line 9 column 13 | items:
Updated by Clark ANDRIANASOLO 3 months ago
- Related to Architecture #25504: Remove webapp technique compilation fallback added
Updated by Alexis Mousset 3 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Félix DALLIDET
- Pull Request set to https://github.com/Normation/rudder/pull/5914
Updated by Clark ANDRIANASOLO 3 months ago
- Assignee changed from Félix DALLIDET to Alexis Mousset
Updated by Alexis Mousset 3 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|2671e597b3e561ada5d0a9db5aef0d388d685a86.
Updated by Vincent MEMBRÉ 2 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.0~rc1 which was released today.
Actions