From 688aca51edb91e2e5900cecfd70beeef234bdaa8 Mon Sep 17 00:00:00 2001 From: Katheryn Satterlee Date: Tue, 23 Jul 2024 10:16:24 -0500 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 17e0d47..3a5b509 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ How to set up your GitOps workflow: 5. Add `FLEET_URL` and `FLEET_API_TOKEN` secrets to your new repository's secrets. Learn how [here](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository). Set `FLEET_URL` to your Fleet instance's URL (ex. https://organization.fleet.com). Set `FLEET_API_TOKEN` to an API token for an API-only user in Fleet. Learn how [here](https://fleetdm.com/docs/using-fleet/fleetctl-cli#create-api-only-user). -6. Add secrets to your repository as well as 'workflow.yml' for `FLEET_GLOBAL_ENROLL_SECRET` and for all environment variables that are mentioned in the global/team YAML files. +6. Add secrets to your repository and update 'workflow.yml' for `FLEET_GLOBAL_ENROLL_SECRET` and for all environment variables that are mentioned in the global/team YAML files. 8. Push your cloned and modified code to your repo.