Rudder

Very good propsotion. The long term solution is to correctly manage technique version, so that a directive doesn't have its technique changed without a clear update path. Your two propositions are also to be done (they are all complementary).

I believe we won't be able to make that level of changes in a released version, but it is important. It's linked with the #12824 and fall into "be able to add metadata to technique parameter, like mandatory or not, input type, default value".

Perhaps field should be mandatory in 4.3/5.0 ? In that case, the change is very simple.

Our parameters are already mandatory :(

When we update an already existing technique version, the content of already existing directive is not validated, causing a new generation with empty values in our case.

• Always bump technique version when upgrading a ncf technique. But htere is a cost to migrate all existing technique
• Add checks on techniques when updated then preventing generation

In both cases it's at least a medium operation

In Rudder 7.x, this is now resolved: adding a new required parameter leads to generation error