mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 00:49:03 +00:00
becb7a3b5b
For #30001 # Details When Fleet is started with logging configured in a way such that the logging plugin has no `config`, clicking "Manage Automations" on the manage queries page results in a 500 page. An example config would be: ``` fdm up --server_address=localhost:8080 --dev --dev_license --logging_debug --osquery_result_log_plugin=stdout --osquery_status_log_plugin=stdout --activity_audit_log_plugin=stdout ``` This PR fixes the issue by adding null protection for cases where the `config` object is empty for the logging plugin. # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [X] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. - [X] Manual QA for all new/changed functionality
1 line
139 B
Text
1 line
139 B
Text
- Fixed issue causing a 500 error when clicking "Manage Automations" from the Queries page when osquery logging has certain configurations
|