Did fleetctl intentionally lose “fleetctl get options” in version 4.2.3? I can do “fleetctl get options” using fleetctl 3.13.0 and it will give me what is now called “agent options”, including per-platform auto_table_construction definitions. The YAML kind is now config, but when I do fleetctl get config I only get the server configuration and not the agent_options details (so SAML, SMTP, etc. setting). But when I do fleetctl get -h in fleetctl 4.2.3, I see no options / agent-options command:

NAME:
   fleetctl get - Get/list resources

USAGE:
   fleetctl get command [command options] [arguments...]

COMMANDS:
   queries, query, q                                             List information about one or more queries
   packs, pack, p                                                List information about one or more packs
   labels, label, l                                              List information about one or more labels
   hosts, host, h                                                List information about one or more hosts
   enroll_secret, enroll_secrets, enroll-secret, enroll-secrets  Retrieve the osquery enroll secrets
   config                                                        Retrieve the Fleet configuration
   carve                                                         Retrieve details for a carve by ID
   carves                                                        Retrieve the file carving sessions
   user_roles, user_role, ur                                     List global and team roles for users
   teams, t                                                      List teams
   help, h                                                       Shows a list of commands or help for one command

OPTIONS:
   --help, -h  show help (default: false)

fleetctl get options was removed in Fleet 4.0.0. agent_options can now be configured using fleetctl get config. An example config yaml doc is here: https://github.com/fleetdm/fleet/blob/main/docs/1-Using-Fleet/configuration-files/multi-file-configuration/organization-settings.yml all the breaking changes made in Fleet 4.0.0 here: https://github.com/fleetdm/fleet/releases/tag/v4.0.0

Thanks! There seems to be an issue retrieving the options, still. I have an agent-options.yml (following the multi-file approach) that I can apply, but I cannot retrieve the agent options. If I run “fleetctl get config” it returns “agent_options: null” even though in my Fleet UI I can see my overrides, ATCs, etc. in the Osquery options section of the Settings tab

Hi Seth, if you’re still experiencing this issue, would you mind opening a new issue on GitHub? Thanks!