Rudder

François ARMAND wrote:

Nicolas CHARLES wrote:

I'm really not sure it should be fixed for "traditionnal" techniques, as they have a different workflow than "meta-techniques with no parametrizables values"

What do you reckon would be the use case of changing metadata.xml content for normal techniques ?

Adding/removing section and variables, essentially. Today, we are saying: "that's an unsupported use case, you have to also update the version number for that". But actually, if somebody DO do that, the result is a broken Rudder (no more promise regeneration working due to missing parameters). And so, the user will have to go to each directive based on that technique to save them again before being able to do anything else.

I'm really not sure we should permit users to add variables in a technique (normal) without changing version number. The risks is high that the values in Directives would not correspond to the values the user expects (or worse, that it might go against what the system needs).

So it would also help in that case: we can (and should) still say: "you really should NOT change metadata.xml without changing the technique version", but at least handle more automatically certain case (variable with default value).

How do you want to prevent the user to edit a file and commit it?

All that is to try to enhanced a case that is clearly NOT RECOMMENDED in the doc, and where we try to mitigate the problems.