Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 22 Packages Projects Releases Wiki Activity

Clarify how Fleet GitOps is supposed to work (#26184)

Browse Source
This commit is contained in:
Victor Lyuboslavsky
2025-02-07 15:02:20 -06:00
committed by GitHub
parent 2eb5119efb
commit a51ecf18ec
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/Configuration/yaml-files.md
+4
View File
@@ -2,6 +2,10 @@
Use Fleet's best practice GitOps workflow to manage your computers as code.
Fleet GitOps is a declarative configuration management system. You define your desired Fleet settings in YAML files and Fleet GitOps makes it so.
Any settings not defined in your YAML files will be reset to the default values, which may include deleting assets such as software packages.
Fleet GitOps workflow is designed to be applied to all teams at once. However, the flow can be customized to only modify specific teams and/or global settings.
To learn how to set up a GitOps workflow see the [Fleet GitOps repo](https://github.com/fleetdm/fleet-gitops).
The following are the required keys in the `default.yml` and any `teams/team-name.yml` files: