User story #4293
closedMigrating from a Technique version to another one in a Directive is long and painful
Added by Dennis Cabooter almost 11 years ago. Updated over 5 years ago.
Description
Migrating directives is too much work. It's enforced to upgrade multiple directives if directives of the same type are applied on the same host. It would be really helpful it it would be possible to upgrade multiple directives in one go.
Note: things can be a little better if handled with API call, since you are avoiding a lot of click and it's working in most cases.
Example about how to do that: https://gist.github.com/fanf/193ca80959dde12bc4d3
Files
Updated by François ARMAND almost 11 years ago
Hello Denis,
Could you please help me understand what's your use case, what is too much pain, and what you would like to be able to do? An example would be really helpful.
Thanks,
Updated by Dennis Cabooter almost 11 years ago
- File rudder-screen.jpg rudder-screen.jpg added
If you look at the attached screenshot, you see a list of 19 directives created from the "Enforce file content" technique. Imagine I want to upgrade all directives from 3.2 to 4.0, it means a lot of clicks.
Updated by Matthieu CERDA almost 11 years ago
- Subject changed from Migrating directives too much work to Migrating from a Technique version to another one in a Directive is long and painful
- Category set to Web - Config management
- Status changed from New to 8
- Assignee set to François ARMAND
- Priority changed from N/A to 2
- Target version set to Ideas (not version specific)
I second that. Having on a node a Directive for technique X and wanting to upgrade to the upper version requires upgrading ALL the directives linked to this Technique before beeing able to redeploy again (else Rudder complains about a version mismatch, as two diff. versions of the Techniques are applied on the same node).
Updated by Nicolas CHARLES almost 11 years ago
We do have an API for managing Directives, couldn't we simply provide a script where user could choose the technique, and the source version and destination version ?
It could cover the easy use case (nothing to add in the directive), and then we could improve it to define variables
Updated by Benoît PECCATTE over 9 years ago
- Related to deleted (User story #5480: Bulk migrate directives to new technique version)
Updated by Benoît PECCATTE over 9 years ago
- Has duplicate User story #5480: Bulk migrate directives to new technique version added
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from Ideas (not version specific) to 2.11.19
Updated by François ARMAND almost 9 years ago
- Related to Bug #5481: Missing fields at directive migration added
Updated by François ARMAND almost 9 years ago
UI ideas from #5481:
"Section: Exclusion/Inclusion" (a new section in the technique version) is by default folded. If you unflod it, you will see your entries :) Maybe it's a good idea to unfold new sections by default. Maybe you can highlight new sections aditionally.
Updated by François ARMAND almost 9 years ago
- Related to Bug #6328: Migrating directives is extremely slow in 3.0 added
Updated by François ARMAND almost 9 years ago
UI/UX ideas from #6328:
Also, mass migration is not possible and right now it's quitte painful to migrate ~ 27 directives. Last but not least; migrating one directive takes ~ 5 clicks, which might not be necessairy.
Updated by Jonathan CLARKE almost 9 years ago
- Translation missing: en.field_tag_list set to Ease of use
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.19 to 2.11.20
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.20 to 2.11.21
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.21 to 2.11.22
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.22 to 2.11.23
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.23 to 2.11.24
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.24 to 308
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 308 to 3.1.14
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Benoît PECCATTE over 7 years ago
- Has duplicate User story #3822: avoid to break everything when migrating a directive to new technique version added
Updated by Benoît PECCATTE over 7 years ago
- Tracker changed from Bug to User story
This is a user story
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Alexis Mousset over 7 years ago
- Related to Bug #2736: We can't apply Directives from different versions of the same Technique on a node added
Updated by François ARMAND over 7 years ago
- Related to Architecture #10625: Don't merge directive from same technique on generation added
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.21 to 3.1.22
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.22 to 3.1.23
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.23 to 3.1.24
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.24 to 3.1.25
Updated by Benoît PECCATTE about 7 years ago
- Target version changed from 3.1.25 to 4.1.9
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.9 to 4.1.10
Updated by François ARMAND almost 7 years ago
- Assignee deleted (
François ARMAND) - Target version changed from 4.1.10 to Ideas (not version specific)
Updated by Alexis Mousset over 5 years ago
- Related to User story #7872: When nothing needs to be done after a directive version migration, Directive should be directly saved added
Updated by Alexis Mousset over 5 years ago
- Related to User story #7873: Highlight new fields when doing a Directive migration 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!