Manage labels via GitOps

[noahtalerman]

Goal

User story
As a _________________________________________,
I want to _________________________________________
so that I can _________________________________________.

Key result

Deliver prioritized customer requests

Original requests

• Ability to manage labels via best practice GitOps #17944

Context

• Product designer: _________________________

Changes

Product

• UI changes: TODO
• CLI (fleetctl) usage changes: TODO
• YAML changes: TODO
• REST API changes: TODO
• Fleet's agent (fleetd) changes: TODO
• Activity changes: TODO
• Permissions changes: TODO
• Changes to paid features or tiers: TODO
• Other reference documentation changes: TODO
• Once shipped, requester has been notified
• Once shipped, dogfooding issue has been filed

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.

[mna]

@noahtalerman note for when that story will be worked on, the #22813 story will have been completed and will prevent deletion of labels referenced by software installers. It will be important for the gitops approach to ensure a similar validation/error message when deleting labels. (for whoever will work on this - this is enforced at the database level via a FK in software_installer_labels)

[noahtalerman]

when that story will be worked on, the #22813 story will have been completed and will prevent deletion of labels referenced by software installers. It will be important for the gitops approach to ensure a similar validation/error message when deleting labels. (for whoever will work on this - this is enforced at the database level via a FK in software_installer_labels)

FYI @rachaelshaw