Patch policies for "Update" card & override how Fleet matches packages and software titles

[marko-lisica]

• @noahtalerman: Plan is to break this story into two separate stories:
  • "Update" card using patch policies
    • Could address this numa request:
      • Fleet-maintained apps: Remove equivalent VPP app by default + cache big apps (e.g. Office) #43613
  • Overrides for matching

---

Goal

User story
As an IT expert,
I want a method to override how Fleet matches the uploaded package to the software title, outside of the code.
so that I can improve matching and merge matching logic without waiting for the next Fleet release.

Changes

Product

• UI changes: TODO
• CLI (fleetctl) usage changes: TODO
• YAML changes: TODO
• REST API changes: TODO
• Fleet's agent (fleetd) changes: TODO
• Fleet server configuration changes: TODO
• Exposed, public API endpoint changes: TODO
• fleetdm.com changes: TODO
• GitOps mode UI changes: TODO
• GitOps generation changes: TODO
• Activity changes: TODO
• Permissions changes: TODO
• Changes to paid features or tiers: TODO
• My device and fleetdm.com/better changes: TODO
• Usage statistics: TODO
• 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:
  • Mention new override method
  • Explain how automatic package matching works, and if it's broken for some apps, that there's way to add override to Fleet repo.
• Database schema migrations: TODO
• Load testing: TODO
• Pre-QA load test: 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

1. Engineer: Added comment to user story confirming successful completion of test plan.
2. QA: Added comment to user story confirming successful completion of test plan.

[marko-lisica]

Hey @lukeheath, heads up I added this story to 4.85.

Context: We want to provide a way for our internal IT experts and customers to improve Fleet's package > software installer matching logic. We had many bugs (I found 10) reported that were related, and we still have a few open.

We already have this in the codebase. This change will make maintenance easier and allow us to handle it independently of the release cycle.

[marko-lisica]

cc @noahtalerman ^ I added it to the product board. I will try to start on it if I have time this sprint.