fleetdm
Add binaries, with their hash and path, to `GET /hosts?populate_software=true`
Goal
| User story |
|---|
As a user hitting the GET /hosts?populate_software=true, |
| I want to see the binary hash and path in addition to the bundle hash and path. |
| so that I can tell Santa which binaries to block. |
Roadmap item
None.
Original requests
- #32363
Resources
More info about customer-ufa's workflow in this Google Doc
Changes
Product
- [ ] UI changes: No changes
- [ ] CLI (fleetctl) usage changes: No changes
- [ ] YAML changes: No changes
- [ ] REST API changes: PR
- [ ] Fleet's agent (fleetd) changes: New column for binary hash in codesign table (TODO: PR to schema)
- [ ] GitOps mode UI changes: No changes
- [ ] GitOps generation changes: No changes
- [ ] Activity changes: No changes
- [ ] Permissions changes: No changes
- [ ] Changes to paid features or tiers: TODO
- [ ] My device and fleetdm.com/better changes: No changes
- [ ] Usage statistics: No changes
- [ ] Other reference documentation changes: TODO
- [ ] First draft of test plan added
- [ ] Once shipped, requester has been notified
- [ ] Once shipped, dogfooding issue has been filed
Engineering
- [ ] Test plan is finalized
- [ ] Contributor API changes: TODO
- [ ] Feature guide changes: TODO
- [ ] Database schema migrations: TODO
- [ ] Load testing: TODO
- [ ] Load testing/osquery-perf improvements: TODO
- [ ] This is a premium only feature: Yes / No
ℹ️ Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".
QA
Risk assessment
- Requires testing in a hosted environment: TODO
- Requires load testing: TODO
- Risk level: Low / High TODO
- Risk description: TODO
Test plan
Make sure to go through the list and consider all events that might be related to this story, so we catch edge cases earlier.
- TODO
- TODO
- TODO
Testing notes
Confirmation
- [ ] Engineer: Added comment to user story confirming successful completion of test plan.
- [ ] QA: Added comment to user story confirming successful completion of test plan.
@noahtalerman It looks like we already have this feature. @dantecatalfamo worked on it.
It looks like we already have this feature. @dantecatalfamo worked on it.
FYI @rachaelshaw
@rachaelshaw @noahtalerman does this design work? if not, we could have @zwass work on it to get it to customer-ufa faster
@zayhanlon we're still doing some research to figure out how the API needs to change, but once we've got an API design ready we'd love @zwass's help on this!
