Rudder

User story #4200

Updated by François ARMAND over 10 years ago

From an implementation point of view, we 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" isComponent="true"> 
       <REPORTKEYS> <PREDEF name="foo"> 
         <VALUE> ... 
         <VALUES><VALUE> val 1 </VALUE><VALUE> val 2 </VALUE> 
       </REPORTKEY> </VALUE></VALUES> 
         ... 
         (alternativly, we also accept for values without ",":) 
         <VALUES val="val1,val2" /> 
         (or a mix of both:) 
         <VALUES val="val1"><VALUE>val,2</VALUE></VALUES> 
     </SECTION> </PREDEF> 
 </pre> 

 Leads to Stands for two variable, NOT updatable by the creation of two variable that will inform Rudder to await for expected reports for component "Some generic method" user, with key name value "val 1" for the first variable et and value "val 2" 

 for the second one.  


 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 Adding a tag in the XML 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 So the "ProvideCsvReportTemplate" nature by parser need to be able to read "PROVIDES_EXPECTED_REPORTS" and set a new flag on technique, and default the existence value of at least "REPORTKEYS" tag. the flag to "false" if the tag is absent.   

Back