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

Update yaml-files.md intro section for legibility and to call out missing or mispelled settings. (#26459)

Browse Source 
Updated top text area for legibility and to call out what happens to
missing or mispelled settings.

These changes were prompted by
https://github.com/fleetdm/fleet/issues/26450

---------

Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
This commit is contained in:
Eugene
2025-02-24 15:44:43 -06:00
committed by GitHub
co-authored by Noah Talerman
parent f9a8910919
commit 9ef382389e
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/Configuration/yaml-files.md
+2 -4
View File
@@ -1,12 +1,10 @@
# YAML files
Use Fleet's best practice GitOps workflow to manage your computers as code.
Use Fleet's best practice GitOps workflow to manage your computers as code. To learn how to set up a GitOps workflow see the [Fleet GitOps repo](https://github.com/fleetdm/fleet-gitops).
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).
Any settings not defined in your YAML files (including missing or mispelled keys) will be reset to the default values, which may include deleting assets such as software packages.
The following are the required keys in the `default.yml` and any `teams/team-name.yml` files: