API design: Deploy security agents to macOS, Windows, and Linux hosts
API design for:
- #14921
This doesn't really make sense to include in the examples, but: the host software API should include "browser" as well when the source is a browser extension (used to display "Browser plugin (<browser>)" as the software type). I think this is currently implemented on the software list page but we forgot to bring that change into the host-specific software page.
This doesn't really make sense to include in the examples, but: the host software API should include "browser" as well when the source is a browser extension (used to display "Browser plugin (
)" as the software type). I think this is currently implemented on the software list page but we forgot to bring that change into the host-specific software page.
@rachaelshaw I think what we want with this new endpoint is to display software titles per host (all installed software titles, no matter what type), plus we're adding status and install action. Do you think that's not clear from the wireframes, should we add dev note or note to issue description?
I think what we want with this new endpoint is to display software titles per host (all installed software titles, no matter what type)
@marko-lisica I think that's clear; just wanted to make sure we also bring in the change from https://github.com/fleetdm/fleet/issues/15429 to include browser in the API when applicable; it doesn't apply to the examples in this PR so didn't make sense to mention in a review comment. (Sorry, should have linked to the issue in my previous comment to make that clearer.)
@marko-lisica, draft docs are missing the changes for the new software_status query param on the list hosts API
@marko-lisica, draft docs are missing the changes for the new
software_statusquery param on the list hosts API
@gillespi314 Added this here.
Hey @rachaelshaw when you get the chance, can you please give this a final review?
We're targeting shipping the Deploy security agents story today.
Thanks!
@marko-lisica @noahtalerman just realized: should we open a fresh PR from this branch? (Looks like this one has been open since March.)
Ah, makes sense. Heads up @marko-lisica. This is so we don't muck w/ the PR open time KPI.
From the handbook:
Here's a short Loom I recorded on how to open a new PR from an existing branch using the GitHub UI.