Skip to content

Adding working GitHub action workflow#26

Merged
getvictor merged 4 commits intomainfrom
victor/fixing-configs
Feb 9, 2024
Merged

Adding working GitHub action workflow#26
getvictor merged 4 commits intomainfrom
victor/fixing-configs

Conversation

@getvictor
Copy link
Copy Markdown
Member

@getvictor getvictor commented Feb 8, 2024

Added GitHub action workflow.
@lucasmrod Please review README.md, workflow.yml, and workflow.sh files

Also, updated indentation to be consistent.

@getvictor getvictor force-pushed the victor/fixing-configs branch from 2721e1d to f4cae1a Compare February 8, 2024 15:49
@getvictor getvictor marked this pull request as ready for review February 8, 2024 15:51
@getvictor getvictor mentioned this pull request Feb 8, 2024
3 tasks
Comment thread README.md Outdated

6. Push your cloned and modified code to your repo.

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. In addition, the workflow will run every 24 hours to ensure that the Fleet configuration is in sync with your git repo.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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. In addition, the workflow will run every 24 hours to ensure that the Fleet configuration is in sync with your git repo.
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.

I see what you're after with this! If any change is made outside of the repo (UI/API/fleetctl), Fleet will get reset (sync w/ the repo).

I think we can cut this feature for v1.

Why? I think it adds more UX complexity. More for the user to keep track of and more for us to explain.

The user can manually trigger the GitHub action if they want to sync right? If so, I think starting w/o the automated run every 24 hours is simpler. The action runs on merge and when you trigger it.

We can get fancy later.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Copy Markdown
Member

@noahtalerman noahtalerman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

YAML interface and README look good to me!

I'll lean on y'all to review the workflow and file and bash script.

@noahtalerman
Copy link
Copy Markdown
Member

Hey @getvictor I think we should make you the CODEOWNER of the workflow file and bash script so you get pinged anytime someone wants to make a change.

What do you think?

I can be CODEOWNERS of the README + YAML files + lib/

If you're cool with that can you please open a PR to CODEOWNERS?

Copy link
Copy Markdown
Member

@lucasmrod lucasmrod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

Comment thread workflow.sh
@getvictor getvictor merged commit b7ce93c into main Feb 9, 2024
@getvictor getvictor deleted the victor/fixing-configs branch February 9, 2024 17:40
getvictor added a commit to fleetdm/fleet that referenced this pull request Feb 9, 2024
Add `fleetctl gitops` command for #13643 

Code review video:
https://www.loom.com/share/7941c51c709b44ccafd618dd05837d99?sid=27b923d7-1393-4396-bac7-30616b2d6de9

fleet-gitops PR that also needs review:
fleetdm/fleet-gitops#26

Working global/team gitops configs that can be used for testing:
https://github.com/fleetdm/fleet-gitops/tree/victor/fixing-configs

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

<!-- Note that API documentation changes are now addressed by the
product design team. -->

- [x] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
- [x] Added/updated tests
- [x] Manual QA for all new/changed functionality
georgekarrv pushed a commit to fleetdm/fleet that referenced this pull request Feb 13, 2024
Add `fleetctl gitops` command for #13643 

Code review video:
https://www.loom.com/share/7941c51c709b44ccafd618dd05837d99?sid=27b923d7-1393-4396-bac7-30616b2d6de9

fleet-gitops PR that also needs review:
fleetdm/fleet-gitops#26

Working global/team gitops configs that can be used for testing:
https://github.com/fleetdm/fleet-gitops/tree/victor/fixing-configs

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

<!-- Note that API documentation changes are now addressed by the
product design team. -->

- [x] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
- [x] Added/updated tests
- [x] Manual QA for all new/changed functionality
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants