User story #9041
closed
Architecture #9108: Add a capabilities files in rudder agent package
Change system promises to call list-compatible-inputs with capabilities file
Added by Alexis Mousset about 8 years ago.
Updated about 8 years ago.
Category:
System techniques
Description
We will add an optional parameter to list-compatible-inputs to filter by Rudder version. We need to use it in the techniques promises.cf.
We will create a capabilities file in /opt/rudder/etc/agent-capabilities.
The promise.cf will call list-compatible-input and pass this file as a parameter.
list-compatible-input will then know when to load a file or not based on these capabilities.
The new list-compatible-input syntax is
list-compatible-inputs [--capability_file <capability_file_path>] [--cfengine <CFEngine_version>] --ncf_path <ncf_framework_path> [common|local]/<nn_directory> [<nn_directory ...]
- Related to User story #9039: Add a static rudder version in rudder agent version added
- Related to User story #9063: Add support for a rudder_version check in list-compatible-input and policy loading added
- Target version changed from 3.2.7 to 3.1.14
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1039
- Related to deleted (User story #9039: Add a static rudder version in rudder agent version)
- Subject changed from Change system promises to call list-compatible-inputs with Rudder version to Change system promises to call list-compatible-inputs with capabilities file
- Description updated (diff)
- Status changed from Pending technical review to Discussion
- Assignee changed from Benoît PECCATTE to Alexis Mousset
We will use a capabilities file instead.
- Target version changed from 3.1.14 to 3.2.7
The new list-compatible-input syntax is
list-compatible-inputs [--capability_file <capability_file_path>] [--cfengine <CFEngine_version>] --ncf_path <ncf_framework_path> [common|local]/<nn_directory> [<nn_directory ...]
If I may, I suggest renaming "--cfengine" to "--agent-version".
Also, the option names "capability_file", "ncf_path", etc should have dashes not underscores, as is common in all UNIX commands (so capability-file, ncf-path, etc)
- Related to User story #9105: Add conditions on features in ncf code loading added
- Status changed from Discussion to In progress
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request changed from https://github.com/Normation/rudder-techniques/pull/1039 to https://github.com/Normation/rudder-techniques/pull/1041
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Related to User story #9066: Use agent_requirements parameter in generic methods documentation added
- Status changed from Pending release to Released
This bug has been fixed in Rudder and 3.2.8/7 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Jonathan CLARKE 
Updated by