User story #3822
closed
avoid to break everything when migrating a directive to new technique version
Description
One rule can not have two directives using different versions of the same technique.
But the only way to upgrade the directives is to migrate each one individually.
As a consequence, the regeneration of rules is broken during the directives migration.
This should be avoided.
It should be possible to upgrade all the directives applied by a rule, from the screen of the rule.
Obviously, this is only possible if new mandatory fields are correctly set up during directive migration: see #3821.
Updated by Vincent MEMBRÉ over 11 years ago
- Category changed from Web - UI & UX to 14
- Assignee set to Jonathan CLARKE
- Target version set to Ideas (not version specific)
This behavior is very linked to how we handle promises generation in Rudder.
We can't generate a promises for two directive based on the same version (theu would be located in the same file, which would implies too many problems.
Maybe a first solution would be to disable/enable only technique based on one Version. and when migrating Directives to an older or newer version, disable the old version and enable the new one
Besises as said in #3821, we will change a lot of things in 2.8, and maybe that problem will be resolved with it too!
Updated by Jonathan CLARKE about 11 years ago
- Assignee deleted (
Jonathan CLARKE)
Updated by Benoît PECCATTE over 9 years ago
- Category changed from 14 to Web - Config management
Updated by Benoît PECCATTE over 7 years ago
- Is duplicate of User story #4293: Migrating from a Technique version to another one in a Directive is long and painful added
Updated by Alexis Mousset over 5 years ago
- Status changed from New to Rejected
We now provide a CLI for mass migration and new fields have default values, closing!