User story #2132
closed
Improve process for upgrading techniques
Added by Nicolas PERRON almost 13 years ago.
Updated over 7 years ago.
Description
Actually, after each Rudder upgrade, the new techniques are located in /opt/rudder/share/policy-templates .
In order to bring these new PT to the webapp, we have to copy them in /var/rudder/configuration-repository/policy-templates/ , commit the good ones and in the webapp to reload PT Library.
We can improve this process by automation when we are sure that:
- Any update of a PT is made in a new version
- No local PT is modified from original, otherwise local PT don't have to be changed
- Trigger a load in the webapp of these new PT
- Assignee set to François ARMAND
- Target version changed from 24 to 47
We have to at least handle a better process for techniques update.
First step: what can be achieved in the 2.5 timeline ?
The first first step is to cleanup the property file to be able to know what are the relevant properties for the git repository configuration.
See issue #2602
- Status changed from New to In progress
- Target version changed from 47 to 50
- Target version changed from 50 to 2.4.0~beta3
- Target version changed from 2.4.0~beta3 to 2.4.0~beta4
We still working on it but i'm not sure that this issue should be in 2.4.
At least, I change it to the next run.
- Target version changed from 2.4.0~beta4 to 2.4.0~rc1
- Status changed from In progress to 2
- Assignee deleted (
François ARMAND)
- Target version changed from 2.4.0~rc1 to 24
- Status changed from 2 to New
- Target version changed from 24 to Ideas (not version specific)
- Project changed from Rudder to 34
- Category deleted (
11)
- Project changed from 34 to Rudder
- Category set to Packaging
- Subject changed from Improve process for upgrading policy templates to Improve process for upgrading techniques
- Description updated (diff)
- Status changed from New to Rejected
This is a development process suggestion, it should not go into a ticket.
Also available in: Atom
PDF