Nico
227bcdf46f
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #35457 # Checklist for submitter - [ ] 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. - [ ] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [ ] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes ## Testing - [x] Added/updated automated tests - [ ] Where appropriate, [automated tests simulate multiple hosts and test for host isolation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/reference/patterns-backend.md#unit-testing) (updates to one hosts's records do not affect another) - [x] QA'd all new/changed functionality manually ### `fleetctl generate-gitops` **UI** <img width="1866" height="787" alt="Screenshot 2026-01-07 at 1 14 45 PM" src="https://github.com/user-attachments/assets/ccb585ee-3074-4ebf-9aaf-6dbdb885cf89" /> **Generated YAML** <img width="694" height="354" alt="Screenshot 2026-01-07 at 1 15 23 PM" src="https://github.com/user-attachments/assets/3867b63d-265d-43bc-bd60-31fb14e83409" /> ### `fleetctl gitops` **Source YAML** I set the start_time to 18:30 and end_time to 19:30 for the first app <img width="359" height="354" alt="Screenshot 2026-01-07 at 1 18 33 PM" src="https://github.com/user-attachments/assets/4cde31e3-aa93-4b75-b296-cc101f507c2a" /> After the command ran, verified both on the UI and DB that the new values were set <img width="790" height="185" alt="Screenshot 2026-01-07 at 1 18 56 PM" src="https://github.com/user-attachments/assets/30d9806c-b26c-4f17-b505-facb7fd0df15" /> <img width="1432" height="708" alt="Screenshot 2026-01-07 at 1 19 15 PM" src="https://github.com/user-attachments/assets/5e123f94-ea69-4403-bba3-abf917cc1a01" /> ## New Fleet configuration settings - [ ] Setting(s) is/are explicitly excluded from GitOps If you didn't check the box above, follow this checklist for GitOps-enabled settings: - [x] Verified that the setting is exported via `fleetctl generate-gitops` - [x] Verified the setting is documented in a separate PR to [the GitOps documentation](https://github.com/fleetdm/fleet/blob/main/docs/Configuration/yaml-files.md#L485): https://github.com/fleetdm/fleet/blob/a79ff22d84466106fccc3818d38f23b9d9dc62df/docs/Configuration/yaml-files.md?plain=1#L538-L540 - [x] Verified that the setting is cleared on the server if it is not supplied in a YAML file (or that it is documented as being optional) - [ ] Verified that any relevant UI is disabled when GitOps mode is enabled ## fleetd/orbit/Fleet Desktop - [ ] Verified compatibility with the latest released version of Fleet (see [Must rule](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/fleetd-development-and-release-strategy.md)) - [ ] If the change applies to only one platform, confirmed that `runtime.GOOS` is used as needed to isolate changes - [ ] Verified that fleetd runs on macOS, Linux and Windows - [ ] Verified auto-update works from the released version of component to the new version (see [tools/tuf/test](../tools/tuf/test/README.md))
Welcome to the "source available" section of the Fleet codebase. Please note files and functionality under this directory are covered by the Fleet EE License, and require a valid Fleet subscription for production use. See the full license for details.