Parameter `order` of the pipeline resource without effect

[FrankNagel]

In classic config mode you 're passing the order parameter of the pipeline resource to the template where it is not used instead of concat::fragment. At least concat::fragment will order them lexicographically and a user can get an order by choosing appropriate titles for the filter resources.

Additionally, when using yaml config this argument does nothing, too. In fact with yaml config there is no
possibility to enforce an order on piplines because in the main config file you include them with a wildcard:

- "/etc/fluent-bit/pipelines/*.yaml"

AFAIK there are no guarantees about the order of the included files.

[deric]

concat::fragment has a parameter named order. See https://github.com/puppetlabs/puppetlabs-concat/blob/main/lib/puppet/type/concat_fragment.rb#L56

[FrankNagel]

Yes, but you're not using this parameter. You pass it instead into the template.

[deric]

Feel free to submit PR to fix it.