Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add additional secrets to README #40

Closed
wants to merge 3 commits into from
Closed

Add additional secrets to README #40

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
258b78a
Add additional secrets to README
ksatter Jul 23, 2024
688aca5
Update README.md
ksatter Jul 23, 2024
17d3ab1
Update README.md
noahtalerman Sep 23, 2024
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
8 changes: 5 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,12 @@ How to set up your GitOps workflow:

4. Create your own GitHub repository.

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).
5. Add the secrets specified at the bottom of [`workflow.yml`](https://github.com/fleetdm/fleet-gitops/blob/main/.github/workflows/workflow.yml) (i.e. `FLEET_URL`) 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. Push your cloned and modified code to your repo.
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.

7. In GitHub, enable the `Apply latest configuration to Fleet` GitHub Actions workflow, and run workflow manually. Now, when anyone pushes a new commit, the action will run and update Fleet.
8. Push your cloned and modified code to your repo.

9. In GitHub, enable the `Apply latest configuration to Fleet` GitHub Actions workflow, and run workflow manually. Now, when anyone pushes a new commit, the action will run and update Fleet.

For all configuration options, go to [GitOps reference](https://fleetdm.com/docs/using-fleet/gitops) in the Fleet documentation.