From a2efbd4aab4e159dd3d549fa2db083b5ef25d7bd Mon Sep 17 00:00:00 2001 From: Magnus Jensen Date: Wed, 18 Mar 2026 11:03:00 -0500 Subject: [PATCH] Remove wrong callout that profiles is resent if secrets change (#41916) This is not behaviour we have today for either Apple or Windows. --- articles/secrets-in-scripts-and-configuration-profiles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/secrets-in-scripts-and-configuration-profiles.md b/articles/secrets-in-scripts-and-configuration-profiles.md index 1c3425152a..4c843d9e57 100644 --- a/articles/secrets-in-scripts-and-configuration-profiles.md +++ b/articles/secrets-in-scripts-and-configuration-profiles.md @@ -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.