Title
#fleet
zwass

zwass

03/03/2021, 6:30 PM
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
6:30 PM
cc @nyanshak
n

nyanshak

03/03/2021, 6:32 PM
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).
6:33 PM
Implementing the proposal would be an excellent solution for my use case 🤷‍♀️
6:34 PM
Osquery provides the full contents of the
osquery_info
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)
defensivedepth

defensivedepth

03/03/2021, 6:42 PM
The proposed solution looks good to me.
s

seph

03/04/2021, 5:33 AM
Pretty sure the enrollment info has been there for years.
5:34 AM
The fancy thing is to make this an option somewhere, but increasing fleet configuration options has other tradeoffs.