Recently a few features around which capabilities an Agent should support were discussed:
I the future there will be more capabilities which either a user from Fleet or directly the administor of an Agent wants to enforce. Further examples are which output can be used, if a queue can be used, variables etc. For this it would be nice to have a generic capabilities feature in the Elastic Agent that we can extend. This issue is to discuss this feature.
For a system administrator to specify the capabilities the Agent has, I think there are at least 2 ways:
- Through config file
- Command line flag on start up
At first, I suggest we start with a capabilities config file. Putting capabilities in a separate config file still allows Fleet to take over the full config file but have the capabilities.yml separate.
The content of the file could look as following:
inputs.allow_list: logfile
inputs.block_list: syslog
# Just an example ...
upgrade.enabled: true
upgrade.bugfix_release: true
upgrade.major_release: false
It would be a flat list of config entries, each describing a capability.
Recently a few features around which capabilities an Agent should support were discussed:
I the future there will be more capabilities which either a user from Fleet or directly the administor of an Agent wants to enforce. Further examples are which output can be used, if a queue can be used, variables etc. For this it would be nice to have a generic capabilities feature in the Elastic Agent that we can extend. This issue is to discuss this feature.
For a system administrator to specify the capabilities the Agent has, I think there are at least 2 ways:
At first, I suggest we start with a capabilities config file. Putting capabilities in a separate config file still allows Fleet to take over the full config file but have the
capabilities.ymlseparate.The content of the file could look as following:
It would be a flat list of config entries, each describing a capability.