Manage Fleet-maintained apps via YAML files (GitOps)

[marko-lisica]

Goal

User story
As an IT admin at Fleet,
I want to use Fleet's best practice GitOps interface to manage Fleet-maintained apps
so that I can dogfood Fleet-maintained apps.

Objective

Mission critical app management

Original requests

#22616

Context

• Product designer: @marko-lisica

Changes

Product

• UI changes: Figma link
• CLI (fleetctl) usage changes: No changes.
• YAML changes: Link to PR
• REST API changes: Link to PR
• Fleet's agent (fleetd) changes: No changes.
• Activity changes: No changes.
• Permissions changes: No changes.
• Changes to paid features or tiers: Available in Fleet Premium.
• Other reference documentation changes: TODO
• Once shipped, requester has been notified

Engineering

• Feature guide changes: TODO
• Database schema migrations: TODO
• Load testing: TODO

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

• Requires load testing: TODO
• Risk level: Low / High TODO
• Risk description: TODO

Manual testing steps

1. Step 1
2. Step 2
3. Step 3

Testing notes

Confirmation

1. Engineer (@____): Added comment to user story confirming successful completion of QA.
2. QA (@____): Added comment to user story confirming successful completion of QA.

[noahtalerman]

Hey @marko-lisica, I just watched your Loom here.

My thoughts:

• Adding the URL to the API makes sense! I think let's take the wireframe-first approach. Can you please see what the URL would look like in the UI? That will help inform the API changes.
• Your script is great! We should start dogfooding that ASAP. I see what you're saying re inline scripts providing a superior UX. Can we make your script work without inline scripts at first? I think this would make this iteration smaller.

[noahtalerman]

@marko-lisica, I left some more feedback in a Loom here.