Better error message: Unrecognized Fleet-maintained app

[noahtalerman]

Goal

User story
As an IT admin who misspelled the Fleet-maintained slug,
I want to see a clear error message that tells me that this misspelled Fleet-maintained app doesn't exist
so that I can quickly fix my YAML.

Roadmap item

None

Original requests

Original request

Resources

Community PR

Changes

Product

• UI changes: No changes
• CLI (fleetctl) usage changes: No changes
• YAML changes:
  • If the user provides a slug for a Fleet-maintained app that does not exist show the following error message:
    • Error: applying software installers for team "XX": “slug” isn’t a supported Fleet-maintained app. See supported apps: https://fleetdm.com/learn-more-about/supported-fleet-maintained-app-slugs
    • @melpike I opened a PR to create redirect
• REST API changes: No changes
• Fleet's agent (fleetd) changes: No changes
• 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: No changes
• My device and fleetdm.com/better changes: No changes
• Usage statistics: No changes
• Other reference documentation changes: No changes
• 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: None
• Feature guide changes: None
• Database schema migrations: None
• Load testing: N/A
• Load testing/osquery-perf improvements: N/A
• This is a premium only feature: Yes

ℹ️  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: No
• Requires load testing: No
• Risk level: Low

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.

1. Try to install a fleet-maintained app with YAML and use a non-existent or misspelled slug to confirm new messaging is reflected.

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.