This was somehow implemented on Monitor software release:
Apache Frontend approach could be used as referecing approach considering the configuration of fluentd should be always done via templates, and never input direct configuration file (or partial file) on parameters. The complexity should be minimalized by the usage of templates.
If the fluentd is part of many SR, create a stack (and not a software like erp5) is better.
From: Ivan Tyagov
For number of projects we need to be able to configure fluentd (https://lab.nexedi.com/nexedi/slapos/blob/master/component/fluentd/buildout.cfg)
Before we do propose something I have following questions:
- Currently fluentd is a "components", is it correct to say that if we add "configuration" to it we should place it as well under "software" (i.e. create NEW https://lab.nexedi.com/nexedi/slapos/blob/master/softwaret/fluentd/software.cfg)?
- How we can pass configuration from slapos master to a software fluentd instance? Is there already a fixed and recommended way of doing - please note that it can be quite complex configuration? Maybe an example can be provided ?