Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/secrets-in-scripts-and-configuration-profiles.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ During a GitOps run, Fleet scans scripts and profiles for variables, pulls their

Profiles with variables aren’t validated during a GitOps dry run because the variables may be missing or incorrect in Fleet. This means they’re more likely to fail during a real run. Best practice: test the script or profile by adding it to Fleet via the UI first.

> When variable values are updated or changed, a profile resend is triggered.
> When variable values are updated or changed, Apple (macOS, iOS, iPadOS) profiles are re-sent. Automatic re-send for Windows profiles is [coming soon](https://github.com/fleetdm/fleet/issues/44852).

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.

Expand Down
Loading