fleet/changes/47412-render-command-line-flags-as-is at 065a52cb9bc664c604eb637fa8efc38e56feb192 - fleet - Gitea: Git with a cup of tea

Discharge7443/fleet

Files

T

Lucas Manuel Rodriguez cf6a8a29c0 Fix command line flags in agent settings UI (#47414 )

Resolves #47412.

- [X] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.

## Testing

- [X] Added/updated automated tests
- [X] QA'd all new/changed functionality manually

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Bug Fixes**
* Agent settings editor now renders empty or null command-line flags
visibly (instead of hiding them), preserving their clearing behavior for
host-level settings.

* **Tests**
* Added tests to validate YAML output and formatting for command-line
flags, missing keys, and related edge cases.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-06-11 11:13:08 -03:00

2 lines

252 B

Plaintext

Raw Blame History

* Fixed the agent settings YAML editor (global and fleet-level) hiding `command_line_flags` behind a comment when set to `{}` or `null` — those values now render as-is, since they have special semantics (they clear all local osquery flags on hosts).