From a51ecf18ec7a73889c5ad0d042eadaf85243bb97 Mon Sep 17 00:00:00 2001 From: Victor Lyuboslavsky Date: Fri, 7 Feb 2025 15:02:20 -0600 Subject: [PATCH] Clarify how Fleet GitOps is supposed to work (#26184) --- docs/Configuration/yaml-files.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/Configuration/yaml-files.md b/docs/Configuration/yaml-files.md index 19bf7218ff..05600b1596 100644 --- a/docs/Configuration/yaml-files.md +++ b/docs/Configuration/yaml-files.md @@ -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: