search

fleetdm / fleet

Open-source platform for IT, security, and infrastructure teams. (Linux, macOS, Chrome, Windows, cloud, data center)
https://fleetdm.com
Other
3.05k stars 423 forks source link

Evaluate GitOps schema and functionality #22470

Open lukeheath opened 3 weeks ago

lukeheath commented 3 weeks ago

Goal

User story
As a Fleet contributor,
I want to understand how Fleet GitOps works in various use cases
so that I can confidently extend its functionality.

Context

  1. Evaluate current GitOps schema for consistency.

    • As we've designed over time, have we maintained consistency?

  2. Opportunities to improve.

    • Are there extensions or modifications we can make to the schema so it is more intuitive?
    • One consideration is our decision to use file path as a unique identified (original design discussion in this snippet).
    • Should we allow optional use of URL as an identifier?

  3. Determine if there are any documentation gaps in GitOps, both externally and internally.

    • Internal contributor may need more detailed documentation on how GitOps behaves in various cases.

  4. Update ticket description with findings and recommended next steps.

lukeheath commented 3 weeks ago

@georgekarrv @noahtalerman I created this issue to make sure we don't lose track of the need to evaluate the GitOps schema and consider if we should amend our path-as-identifier decision before we remove the experimental label from the software features.