Project

General

Profile

Actions
Copy link

User story #4293

closed

Migrating 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.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
Ideas (not version specific)
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

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

rudder-screen.jpg (231 KB) rudder-screen.jpg Dennis Cabooter, 2013-12-30 10:54

Subtasks 9 (0 open — 9 closed)

Bug #4282: Directive migration doesn't handle default valuesReleasedFrançois ARMAND2013-12-19Actions
Bug #7871: Directive version migration should set default values if presentRejectedVincent MEMBRÉ2016-02-04Actions
User story #7874: Allow bulk migration of techniques RejectedVincent MEMBRÉActions
Bug #7924: Several techniques are missing explicit default values for booleansReleasedBenoît PECCATTE2016-02-03Actions
Bug #7869: Add a default value for COPYFILE_STICKY_FOLDER for copyGitFile 2.1ReleasedBenoît PECCATTE2016-02-03Actions
Bug #7925: Several techniques are missing explicit default values for booleans - branch 3.0ReleasedBenoît PECCATTE2016-02-15Actions
Bug #7953: Technique "Download a file from the shared folder" is missing a default value for permissions in version >= 1.6ReleasedBenoît PECCATTE2016-02-15Actions
Bug #7955: Technique "Download a file from the shared folder" is missing a default value for permissions in version 2.0ReleasedBenoît PECCATTE2016-02-15Actions
User story #7959: "rudder technique migrate" command to automatically upgrade all directives to a newer technique versionRejectedAlexis MoussetActions

Related issues 8 (2 open — 6 closed)

Related to Rudder - Bug #5481: Missing fields at directive migrationRejected2014-09-04Actions
Related to Rudder - Bug #6328: Migrating directives is extremely slow in 3.0Rejected2015-03-03Actions
Related to Rudder - Bug #2736: We can't apply Directives from different versions of the same Technique on a nodeRejectedActions
Related to Rudder - Architecture #10625: Don't merge directive from same technique on generationReleasedVincent MEMBRÉActions
Related to Rudder - User story #7872: When nothing needs to be done after a directive version migration, Directive should be directly savedNewVincent MEMBRÉActions
Related to Rudder - User story #7873: Highlight new fields when doing a Directive migrationNewVincent MEMBRÉActions
Has duplicate Rudder - User story #5480: Bulk migrate directives to new technique versionRejectedDennis Cabooter2014-09-04Actions
Has duplicate Rudder - User story #3822: avoid to break everything when migrating a directive to new technique versionRejectedActions
Actions
Copy link
 #1

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,

Actions
Copy link
 #2

Updated by Dennis Cabooter almost 11 years ago

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.

Actions
Copy link
 #3

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).

Actions
Copy link
 #4

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

Actions
Copy link
 #5

Updated by Benoît PECCATTE over 9 years ago

  • Status changed from 8 to New
Actions
Copy link
 #6

Updated by Benoît PECCATTE over 9 years ago

  • Related to deleted (User story #5480: Bulk migrate directives to new technique version)
Actions
Copy link
 #7

Updated by Benoît PECCATTE over 9 years ago

  • Has duplicate User story #5480: Bulk migrate directives to new technique version added
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from Ideas (not version specific) to 2.11.19
Actions
Copy link
 #9

Updated by François ARMAND almost 9 years ago

  • Related to Bug #5481: Missing fields at directive migration added
Actions
Copy link
 #10

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.

Actions
Copy link
 #11

Updated by François ARMAND almost 9 years ago

  • Related to Bug #6328: Migrating directives is extremely slow in 3.0 added
Actions
Copy link
 #12

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.

Actions
Copy link
 #13

Updated by Jonathan CLARKE almost 9 years ago

  • Translation missing: en.field_tag_list set to Ease of use
Actions
Copy link
 #14

Updated by François ARMAND almost 9 years ago

  • Description updated (diff)
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.24 to 308
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 308 to 3.1.14
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #27

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
Actions
Copy link
 #28

Updated by Benoît PECCATTE over 7 years ago

  • Tracker changed from Bug to User story

This is a user story

Actions
Copy link
 #29

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions
Copy link
 #30

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
Actions
Copy link
 #31

Updated by François ARMAND over 7 years ago

  • Related to Architecture #10625: Don't merge directive from same technique on generation added
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions
Copy link
 #33

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions
Copy link
 #34

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions
Copy link
 #35

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions
Copy link
 #36

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions
Copy link
 #37

Updated by Benoît PECCATTE about 7 years ago

  • Target version changed from 3.1.25 to 4.1.9
Actions
Copy link
 #38

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions
Copy link
 #39

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)
Actions
Copy link
 #40

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
Actions
Copy link
 #41

Updated by Alexis Mousset over 5 years ago

  • Related to User story #7873: Highlight new fields when doing a Directive migration added
Actions
Copy link
 #42

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!

Actions
Copy link

Also available in: Atom PDF