User story #25600: Compliance reporting with type worst-case-percent is not known by rudderc - Rudder - Issue Tracker

Actions

Copy link

User story #25600

closed

User story #25383: Worst report takes the worst component instead of block

Compliance reporting with type worst-case-percent is not known by rudderc

Added by Clark ANDRIANASOLO about 2 months ago. Updated about 1 month ago.

Status:

Released

Priority:

N/A

Assignee:

Alexis Mousset

Category:

Techniques

Target version:

8.2.0~rc1

Pull Request:

https://github.com/Normation/rudder/p...

UX impact:

I dislike using that feature

Suggestion strength:

User visibility:

Effort required:

Small

Name check:

To do

Fix check:

To do

Regression:

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:

Related issues 1 (0 open — 1 closed)