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

Jump to bottom

Validate our base fleetd installers every 24 hours #19126

Open
2 tasks
lukeheath opened this issue May 17, 2024 · 1 comment
Open
2 tasks

Validate our base fleetd installers every 24 hours #19126

lukeheath opened this issue May 17, 2024 · 1 comment
Labels
~csa Issue was created by or deemed important by the Customer Solutions Architect. ~engineering-initiated Engineering-initiated story, such as a bug, refactor, or contributor experience improvement. #g-endpoint-ops Endpoint ops product group ~gitops Related to functionality that enables automation of Fleet via userland git repo(s). :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature

Comments

@lukeheath
Copy link
Member

lukeheath commented May 17, 2024 •
edited

Goal

User story
As a Fleet maintainer,
I want to run a workflow every 24 hours that validates all file manifests hosted by Fleet
so that I can respond quickly if there is ever a checksum mismatch.

Context

Changes

Engineering

  • Create a scheduled GitHub workflow that runs every 24 hours and validates files in R2 to confirm that the chemsums in the manifest file match the checksums in the files.
  • Or, update the existing release-fleetd-base.yml to validate at the end of the job.
  • Trigger alert in #help-p1 on failure to validate.
@lukeheath lukeheath added ~gitops Related to functionality that enables automation of Fleet via userland git repo(s). story A user story defining an entire feature :product Product Design department (shows up on 🦢 Drafting board) #g-endpoint-ops Endpoint ops product group ~engineering-initiated Engineering-initiated story, such as a bug, refactor, or contributor experience improvement. labels May 17, 2024
@lukeheath
Copy link
Member Author

@sharon-fdm I am prioritizing this engineering-initiated story for the next sprint. Please make sure to estimate and bring into the next sprint.

@lukeheath lukeheath changed the title Create GitHub workflow that validates our base agent installers every 24 hours Create GitHub workflow that validates our base agent installer checksums every 24 hours May 17, 2024
@nonpunctual nonpunctual added the ~csa Issue was created by or deemed important by the Customer Solutions Architect. label May 17, 2024
@lukeheath lukeheath changed the title Create GitHub workflow that validates our base agent installer checksums every 24 hours Use GitHub actions to validate our base fleetd installers' checksums every 24 hours May 17, 2024
@lukeheath lukeheath changed the title Use GitHub actions to validate our base fleetd installers' checksums every 24 hours Validate our base fleetd installers' checksums every 24 hours May 17, 2024
@lukeheath lukeheath changed the title Validate our base fleetd installers' checksums every 24 hours Validate our base fleetd installers every 24 hours May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
~csa Issue was created by or deemed important by the Customer Solutions Architect. ~engineering-initiated Engineering-initiated story, such as a bug, refactor, or contributor experience improvement. #g-endpoint-ops Endpoint ops product group ~gitops Related to functionality that enables automation of Fleet via userland git repo(s). :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lukeheath @nonpunctual