Bug #15032
closed
Add capabilities as base conditions
Added by Alexis Mousset almost 5 years ago.
Updated over 4 years ago.
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Description
This will allow having different policies based on agent capabilities, mainly for http reporting for now.
cfengine
yaml
xml
http_reporting
...
- Target version changed from 6.0.0~beta1 to 6.0.0
- Subject changed from Add rudder version as cfengine class starting from 5.1 to Add rudder version as cfengine class starting from 6.0
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Small
- Subject changed from Add rudder version as cfengine class starting from 6.0 to Add capabilities as system classes
- 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/1555
- Status changed from Pending technical review to Pending release
- Subject changed from Add capabilities as system classes to Add capabilities as base conditions
- Description updated (diff)
All the defined classes will follow the syntax: agent_capability_${capability_name}
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.0 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by