Revision e5c904f0
Added by Raphaël Gauthier almost 7 years ago
22_configuration_management/38_technique_editor.txt | ||
---|---|---|
- This method only take one parameter, the name of the package to install. So here, fill in the *package_name* field with the value _ntp_.
|
||
|
||
* File from template (You can find it in the *File category*)
|
||
- This method take two parameters. The first one corresponds to the absolute path of the source file containing a template to be expanded. We are going to use a Rudder variable here to get the correct path. Fill in the *source_template* field with the value _${path_technique}/templates/ntp.conf_.
|
||
The second corresponds to the absolute path of the destination file. Fill in with the value _/etc/ntp.conf_.
|
||
- This method take two parameters. The first one corresponds to the absolute path of the source file containing a template to be expanded. We are going to use a Rudder variable here to get the correct path. Fill in the *source_template* field with the value _$\{path_technique\}/templates/ntp.conf_.
|
||
- The second corresponds to the absolute path of the destination file. Fill in with the value _/etc/ntp.conf_.
|
||
|
||
* Service restart (You can find it in the *Service category*)
|
||
- This method only take one parameter, the name of the service we want to restart. So here, fill in the *service_name* field with the value _ntp_.
|
||
... | ... | |
|
||
===== 3. Save and apply your technique
|
||
|
||
And… It’s already done. Rather fast, right? Don't forget to save. Now you can see it in the *Directives _tree_*, and use that it to create a Directive that will be applied on your _Nodes_ thanks to a _Rule_.
|
||
And… It’s already done. Rather fast, right? Don't forget to save. Now you can see it in the *Directives _tree_*, and use it to create a Directive that will be applied on your _Nodes_ thanks to a _Rule_.
|
||
|
Also available in: Unified diff
Fixes #10710: Missing information in Technique editor doc