User story #1775
closed
Document the PT upgrade procedure
Added by Fabrice FLORE-THÉBAULT over 12 years ago.
Updated about 9 years ago.
Description
Our packages install PTs in /opt/rudder/share/policy-templates, but the library read by Rudder, which is git-managed, will be moved to /var/rudder. The PT updates coming with Rudder will then go in /opt/rudder/share/policy-templates but will need a manual import in the lib that is in git, to make the user validate manually the updates. We will notify the user with an "echo" in the packaging!
+ A / MCE / Add git as a dependency in the rudder-policy-templates package
- Target version changed from 21 to 23
- Target version changed from 23 to 2.3.0
- Assignee deleted (
Fabrice FLORE-THÉBAULT)
- Target version changed from 2.3.0 to 2.3.1
- Target version changed from 2.3.1 to 2.3.2
- Target version changed from 2.3.2 to 2.3.3
- Target version changed from 2.3.3 to 2.3.4
- Target version changed from 2.3.4 to 2.3.5
- Target version changed from 2.3.5 to 2.3.6
- Target version changed from 2.3.6 to 2.3.7
- Status changed from 2 to Discussion
- Target version changed from 2.3.7 to 2.3.8
This ticket needs translating.
It describe a workflow about an old migration of policy templates. Does it still relevent ?
- Priority changed from 4 to 2
Yes, it is still very relevant. This is poorly documented (and thought out?) part of Rudder!
- Target version changed from 2.3.8 to Ideas (not version specific)
- Status changed from Discussion to Rejected
- Project changed from 30 to Rudder
- Category set to Documentation
- Subject changed from document PT upgrade to Document the PT upgrade procedure
- Description updated (diff)
Also available in: Atom
PDF
Updated by 
Updated by Matthieu CERDA 
Updated by 
Updated by Nicolas PERRON 
Updated by