User story #4200
Updated by François ARMAND over 10 years ago
From an implementation point of view, we need to add a new variable type that allows to represent a variable whose values are provided in the spec.
Here, we don't talk about a default value, but a list of variables with a value, maybe different each time.
Those variable will be use to know what are the expected report keys name.
So, the following spec:
<pre>
<SECTION name="Some generic method"> method" isComponent="true">
<REPORTKEYS>
<VALUE> val 1 </VALUE><VALUE> val 2 </VALUE>
</REPORTKEY>
</SECTION>
</pre>
Leads to the creation of two variable that will inform Rudder to await for expected reports for component "Some generic method" with key name "val 1" and "val 2"
Some more specification details:
- only one reportkeys is allowed for a given section
- a section with a <REPORTKEYS> element is marked "multivalued=true, isComponent=true, componentKey=[calculated from section name]"
Also, for the integration with ncf, new Technique will comes with a template of expected reports.
We need to be able to know in a Technique object if the Technique is a new one, with the CSV file, or an old one, without it.
Knowing that at parsing time for that will allow to validate the presence of the CSV at the expeted place and adapt the expected report process to use it.
We can infer the "ProvideCsvReportTemplate" nature by the existence of at least "REPORTKEYS" tag.