User story #12614
closed
- Target version changed from Ideas (not version specific) to 4.1.12
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-agent/pull/174
- Target version changed from 4.1.12 to 4.3.2
- Pull Request changed from https://github.com/Normation/rudder-agent/pull/174 to https://github.com/Normation/rudder-agent/pull/175
- Status changed from Pending technical review to Pending release
- Subject changed from Update the technique migration script to Add scripts to help migrate techniques
2 bash scripts where added to automate the technique migration:
- rudder directive replace [-iIvdq] [-c] -o <old-directive-id> -n <new-directive>
Will replace in all the rules the directive <old-directive-id> by <new-directive-id>. Options -v is for verbose mode and -c to disable the colored output.
- rudder technique migrate [-iIcvd] -n technique_name [target_technique_version]
Will migrate all the directives based on the technique <technique_name> in the version [target_technique_version]. This is equivalent to a manual migration via the interface.
If no [target_technique_version] is given it will look for the latest available one.
/!\ The scripts are minimalist and will only raise an error when the actions fail and not execute any kind of tests to ensure that the changes are coherent.
- Subject changed from Add scripts to help migrate techniques to Add scripts to help migrate techniques to rudder server command
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.2 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by