evaluation order of cluster sub parts after config reload

[iceisfun]

it seems like when items are re-ordered in the [clusters] section and a configuration is reloaded the new order is not honored.

would it be unreasonable to add a "order" to frontends, or evaluate them in config order after a config reload?

[Keksoj]

I'm curious: what does your config look like, before and after this reordering?

[FlorentinDUBOIS]

@iceisfun friendly ping on @Keksoj's question above — could you share the [clusters] config snippet (or the relevant frontend entries) before and after reordering, plus the matching reload command? With those we can repro the eval-order behavior you saw and decide whether to add an explicit ordering knob or fix the reload pipeline.