Problem when updating a category name for Technique Management in /var/rudder
If we edit a technique category :
% vim /var/rudder/configuration-repository/techniques/systemSettings/networking/category.xml
And then change the name of that category :
<xml> <!-- <name>Networking</name> --> <name>Networking new name</name> ... </xml>
% cd /var/rudder/configuration-repository % git add . % git commit -m "Change category name"
And then if we go on Technique Library Management in the user interface, and press "Reload", the category name hasn't changed.
If we want the "Reload" to work, we need to edit a technique. For example a technique name :
% vim /var/rudder/configuration-repository/techniques/systemSettings/networking/nfsClient/1.0/metadata.xml
And then change the technique's name :
<TECHNIQUE name="NFS Client new name"> <!-- <TECHNIQUE name="NFS Client"> --> ... </TECHNIQUE>
% cd /var/rudder/configuration-repository % git add . % git commit -m "Change technique name"
Now if we press "Reload", the technique change and the category name change are visible.
A other change must be there (i.e. change technique name) if we want to update a category in the user interface. This behavior has to be fixed.
Updated by Vincent MEMBRÉ over 7 years ago
I investigated on that bug.
Technique library reloading only take modification on technique file into accounts, not category file.
So for the reloading process when there is only modification on category file, there is no modification so there is no update of the technique library.
A simple solution, would be to update library even if there's no modification, but that would imply a lot of requests.
A better solution, would need a lot of work, and maybe to redefine how we reload the technique library, which may be to important for that beta