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

Remove wrong callout that profiles is resent if secrets change (#41916)

Browse Source 
This is not behaviour we have today for either Apple or Windows.
This commit is contained in:
Magnus Jensen
2026-03-18 12:03:00 -04:00
committed by GitHub
parent 4abd911000
commit a2efbd4aab
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
articles/secrets-in-scripts-and-configuration-profiles.md
+1 -1
View File
@@ -44,7 +44,7 @@ Profiles with variables aren’t validated during a GitOps dry run because the v
Some variables trigger a profile resend when their value changes. See which variables support this in the [YAML reference docs](https://fleetdm.com/docs/configuration/yaml-files#variables).
If a variable is a secret (for example, an API token), prefix it with FLEET_SECRET_. This masks the value when viewed or downloaded from the Fleet UI or API. If a secret’s value changes, the profile is resent to hosts.
If a variable is a secret (for example, an API token), prefix it with FLEET_SECRET_. This masks the value when viewed or downloaded from the Fleet UI or API.
Variables aren't removed on GitOps runs. To remove a variable, delete it on the `Controls` > `Variables` page.