Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

It appears that Fleet recently stopped honoring the `FLEET_PACKAGING_GLOBAL_ENROLL_SECRET` environment variable. What's the ideal way to specify an enrollment secret when starting Fleet?

Hello Eric! Great question. I'm going to take a look and see if I can confirm the change that was made and if we have any documented alternatives.

Would you mind confirming, this is the enrollment secret you're using to enroll new hosts in Fleet?

That's correct. I reverted back to v4.70.0 and that variable is honored again.

Glad to hear reverting worked! There is a potential we might be looking at a bug here. 

Just to confirm the version that you were on before reverting? 4.71.0? 

For enrolling hosts generally we would be using `FLEET_GLOBAL_ENROLLMENT_SECRET` as the enrollment secret variable, but I don’t believe there’s been any change there recently. 

Comparing config.go for <https://github.com/fleetdm/fleet/blob/main/server/config/config.go#L583|main> versus <https://github.com/fleetdm/fleet/blob/fleet-v4.70.0/server/config/config.go|4.70.0> suggests "fleet sandboxes" have gone away, and that somehow matters.

Checking back in on this <@U09720NSB43> Apologies as I was out for a few days and catching back up on stuff. I'd like to get a bug report submitted for this today. I believe I have all the information I need to get it submitted, but if you think there's anything else worth adding for context in the bug report let me know.

Especially if you could provide the steps to reproduce the issue they can be used to verify we got things fixed, etc..