👋 I'm doing some maintenance on an old Kolide config that is now used w/ Fleet and I'm getting an error message:

Error: applying fleet config: PATCH /api/latest/fleet/config received status 400 Bad Request: unsupported key provided: "force"

We have

force: true

in the

options.yaml

file. AFAIK this is still a valid osquery flag - does the error just mean that it's not a supported flag in the config?

Hi @sean.cavanaugh! That error indicates that you're using a configuration option that isn't valid in the current version of

osquery

. Since

--force

is a command-line flag, and osquery has started enforcing not setting command-line flags in config, it's flagged by Fleet as an invalid option. You can include

--force

when applying your config if you're using a version of osquery that will allow that flag to be set:

fleetctl apply --force -f config.yaml

More info: https://fleetdm.com/docs/using-fleet/configuration-files#agent-options

@Kathy Satterlee per "osquery has started enforcing not setting command-line flags in config", what's the preferred method for setting cmdline flags now?