User story #4171
closed
Techniques and software should be de-coupled
Added by Dennis Cabooter about 11 years ago.
Updated over 6 years ago.
Description
Techniques and software should be de-coupled. Techniques can be managed by git solely. Should be really nice if there was an official cli script to upgrade to the latest and greatest techniques, instead of waiting for a new software release. In this way new techniques and bug fixes can be published much faster.
Another approach would be to manage it from the webapp, with some buttons:
- fetch latest techniques
- install latest techniques
- rollback to previous techniques
- Assignee set to Jonathan CLARKE
- Target version changed from 2.8.2 to Ideas (not version specific)
A quick win to me : ask the user on upgrade of rudder-techniques if he wants to upgrade technique automatically.
This would clearly ease the upgrade process, or at least remind the user that he has to check his techniques!
Jon, what do you think a of it ? Until we got a better idea to handle this ?
If so, targeting it to 2.9?
- Status changed from New to 8
- Priority changed from N/A to 2
Vincent MEMBRÉ wrote:
A quick win to me : ask the user on upgrade of rudder-techniques if he wants to upgrade technique automatically.
This would clearly ease the upgrade process, or at least remind the user that he has to check his techniques!
Jon, what do you think a of it ? Until we got a better idea to handle this ?
If so, targeting it to 2.9?
Great idea... but technically impossible. RPM has no mechanism to ask the user a question. We could do this in .debs because apt-get/aptitude support this (dpkg actually), but I don't like the idea of doing it in once place and not everywhere.
However! I see another quick win - just build this script and include in the distribution. At least that way it can be run!
- Status changed from 8 to New
- Category set to Techniques
- Assignee deleted (
Jonathan CLARKE)
- Status changed from New to Rejected
Theye are.
And there is a script to upgrade separately now, see #11059
- Is duplicate of User story #11059: Create a rudder server upgrade-techniques commands added
- Status changed from Rejected to New
Benoît PECCATTE wrote:
Theye are.
And there is a script to upgrade separately now, see #11059
I don't see how this script answers the ticket - to have new techniques, we need to upgrade Rudder, and the script in the related ticket does copy from /opt/rudder/share/techniques (so, from the software) to the local git
What this ticket ask is to be able to update the Techniques without updating Rudder, so fetching from a git repository/marketplace/something else
I'm reopening
- Status changed from New to Released
This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE 
Updated by 
Updated by