Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-04-21 13:37:30 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 91

Fix typo in GitOps migration documentation

Browse source
This commit is contained in:
Dale Ribeiro 2026-04-20 17:54:22 -04:00 committed by GitHub
parent b2b8254e32
commit 9b2b79eebe
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
articles/migrating-to-gitops-using-fleetctl.md
View file

@ -40,7 +40,7 @@ To have `generate-gitops` output sensitive info in plaintext in your files, you
The `generate-gitops` tool includes a few other options to make migrating to GitOps easier:
- `--print` : Print the configuration to `stdout` rather than to files.
- `--team` : **Available in Fleet Premium.** Only output the configuration files of the fleet with the specified name. Global or "Unassgined" configuration may be output using `--team global` or `--team no-team`.
- `--team` : **Available in Fleet Premium.** Only output the configuration files of the fleet with the specified name. Global or "Unassigned" configuration may be output using `--team global` or `--team no-team`.
- `--key` : Display the value of a specific, dot-delimited key, e.g. `agent_options.config.decorators`. Searches for the given key in the global configuration by default; use in conjunction with `--team` to output config from a specific fleet.
See `fleetctl generate-gitops --help` for all options.
@ -56,4 +56,4 @@ See `fleetctl generate-gitops --help` for all options.
<meta name="authorFullName" value="Scott Gress">
<meta name="publishedOn" value="2025-05-22">
<meta name="articleTitle" value="Migrating to GitOps using fleetctl">
<meta name="description" value="Instructions for migrating your Fleet configuration to GitOps.">
<meta name="description" value="Instructions for migrating your Fleet configuration to GitOps.">