Feature request: Different config options per labels

[vector-sec]

Per this comment in #1738 it seems that supported osqueryd configuration options per label hasn't been implemented.

Could this feature request be revisited?

Perhaps the order of applying label-specific configs could be defined by one of the following possibilities:

• Tracking label-specific config processing order in the Fleet database
• Applying label-specific config processing in alphabetical order by the Label's name

I think that as long as the application logic is consistent, this would be a valuable feature to have for teams that are trying to use Fleet to manage a wider variety of systems that can't rely on platform specific configuration options.

Thanks for taking the time to read this and for the work you have put into Fleet already!

I'm happy to help brainstorm about how this could be implemented.

[crimsonknave]

I have a single Fleet server that has hosts in many datacenters/AWS sites enrolled. I am trying to specify a site specific kafka broker for a specific region/datacenter. This is a pretty large requirement from a data governance/locality perspective. From what I can tell the best way to do this would be via a config override per host.

Is this feature something that's likely to be implemented any time soon?