Hi folks, looking for some input on handling "dupl...
# fleet
Hi folks, looking for some input on handling "duplicate" host enrollment. Please check out the issue and comment there or here: https://github.com/fleetdm/fleet/issues/373
cc @nyanshak
I don't really have any problems with the proposal. I already use the 'host expiry' feature to age out MIA hosts (which is super useful with ephemeral hosts).
Implementing the proposal would be an excellent solution for my use case 🤷‍♀️
Osquery provides the full contents of the
table in each enrollment request
^ Is there a minimum version of osquery where that started happening or has this been the behavior with osquery tls enrollment forever? (try to keep up to date, but just want to make sure this assumption always holds)
The proposed solution looks good to me.
Pretty sure the enrollment info has been there for years.
The fancy thing is to make this an option somewhere, but increasing fleet configuration options has other tradeoffs.