User story #5472
open
Be able to group several modifications under only one save (change request)
Added by Olivier Mauras about 10 years ago.
Updated 2 months ago.
Category:
Web - Config management
Description
Hello,
Following our discussion on IRC, it would be great to have a way to commit multiple actions at once instead of having Rudder launch a generation each time.
Example 1 - New service implementation:
- Create a new group and add nodes in there
- Create a directive to manage services
- Create a directive to handle packages
- Create a directive to manage configuration files
- Finally add a rule to apply directives on the group
This amounts to 5 non really needed generations that could have easily been replaced by only one when done with the work
Example 2 - Heavy modification of an existing service:
For each directive changes on this service, i'll have a generation running, this could lead to nodes fetching intermediate configuration that could potentially break the service.
This could be avoided by having a way to commit when the work is done and nodes would only sync a clean configuration.
Thanks,
Olivier
Related issues
2 (2 open — 0 closed)
Sounds like database transactions. +1
- Subject changed from Commit button to Commit button to groups modifications under only one change request
- Target version changed from 140 to 3.0.0~beta1
We thought at that use case, and we may have a solution really neat for user workflow: just add a "grace period" before a promise generation (say 5 minutes for the sack of the example).
With that, the generation is triggered only after the expiration of the grace period. New modification saved during the grace period set back the counter to 0.
If the user want to trigger the generation without waiting 5 minutes, it can be done manually.
It seems to match quite nicelly your use case. Do you see some drawback we missed with that solution ?
To answer myself: there is at least one drawback which choosing a correct time for the grace period.
A too short one will forbid to actually do any other relevant update. A too long one introduce a big delay between modification and actual generation - not exactly like if we didn't have already a good share of 5min delays.
- Target version changed from 3.0.0~beta1 to 3.0.0~beta2
- Target version changed from 3.0.0~beta2 to 3.1.0~beta1
This won't be done in 3.0.
- Target version changed from 3.1.0~beta1 to 3.1.0~rc1
- Target version changed from 3.1.0~rc1 to 3.1.0
- Target version changed from 3.1.0 to 3.1.1
- Target version changed from 3.1.1 to 3.1.2
- Target version changed from 3.1.2 to Ideas (not version specific)
- Related to User story #7923: Combine multiple Change Requests into a bundled one in the Change- and Validation workflow added
- Subject changed from Commit button to groups modifications under only one change request to Be able to group severam modifications under only one save (change request)
- Assignee deleted (
François ARMAND)
- Subject changed from Be able to group severam modifications under only one save (change request) to Be able to group several modifications under only one save (change request)
- Priority changed from 2 to N/A
Also available in: Atom
PDF