Description
Fluentd and Fluentbit support the use of @include so that large configuration files can be decomposed. This currently doesn't work for YAML configuration files. However, given YAML files are highly sensitive to change, it makes it all the more valuable for the ability to break the sections into separate inclusions
Note without this it could impact the ability for people to migrate from the legacy format to YAML
Describe the solution you'd like
suggest a file preprocessor that performs simple text substitution before processing the file as a YAML file. This would make the mechanism pretty simple to achieve, even if that means a more elegant needs to follow later.
Alternatively, you could simplify both YAML and traditional formats by processing the use of @include as a substitution preprocessor and creating a temporary config file; this would then mean that you could implement the inclusions at the same level of granularity as Fluentd. The upside of this approach is that then the result of the inclusions could also be easily seen in the event of an error
Describe alternatives you've considered
YAML-type declaration for inclusion. While syntactically correct would be less consistent and may limit the ability to migrate