-
Notifications
You must be signed in to change notification settings - Fork 886
Implement orbit auto-update automation in Github Actions #10334
Copy link
Copy link
Closed as not planned
Labels
#g-endpoint-opsEndpoint ops product groupEndpoint ops product groupstale~agentRelated to Fleet's osquery runtime and agent autoupdater (Orbit)Related to Fleet's osquery runtime and agent autoupdater (Orbit)~backendBackend-related issue.Backend-related issue.~engineering-initiatedEngineering-initiated story, such as a bug, refactor, or contributor experience improvement.Engineering-initiated story, such as a bug, refactor, or contributor experience improvement.~github actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions code
Metadata
Metadata
Assignees
Labels
#g-endpoint-opsEndpoint ops product groupEndpoint ops product groupstale~agentRelated to Fleet's osquery runtime and agent autoupdater (Orbit)Related to Fleet's osquery runtime and agent autoupdater (Orbit)~backendBackend-related issue.Backend-related issue.~engineering-initiatedEngineering-initiated story, such as a bug, refactor, or contributor experience improvement.Engineering-initiated story, such as a bug, refactor, or contributor experience improvement.~github actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions code
To prevent issues like #10300 from happening again the future we need automation that will test the auto-update mechanism of Orbit in every PR where Orbit code is modified.
Fleet and Orbit is the current Orbit automation. We should attempt to add an auto-update check on the three OSs on such Github Action.
If full automation is not possible with Github Actions then we need to document how developers should test the auto-update mechanism in https://github.com/fleetdm/fleet/blob/main/tools/tuf/test/Orbit-auto-update-test-guide.md#L18