Manage EULAs via GitOps

[mason-buettner]

• @noahtalerman: User requested this because they want to manage all Fleet configurations, including the EULA, through a GitOps workflow for consistency, version control, and automation.
  • @noahtalerman: In the interim they are uploading the EULA manually via the Fleet UI or API whenever changes are needed, which introduces risk and inconsistency in their automation pipeline.
  • @noahtalerman: Eventually Fleet could add the ability to point to your EULA's path in your lib/ or url.

---

[Sampfluger88]

Linked to Unthread ticket:

Inquiry about GitOps approach for modifying EULA #5205

[noahtalerman]

Problem

Fleet's GitOps workflow provides users the ability to manage many areas of their Fleet server configurations, but to manage the EULA you must use the API or UI.

What have you tried?

customer-pingali has updated the EULA their organization via the API and UI, but would like to move the process into their GitOps workflow.

Potential solutions

Fleet's GitOps workflow should have support for modifying the EULA.

What is the expected workflow as a result of your proposal?

I add the updated EULA to my GitOps repo > I link the EULA in my configuration file > When my GitOps configuration synchronizes, the updated EULA is pushed.

[noahtalerman]

@Patagonia121 we shipped support for specifying the EULA (end users see during new Mac setup) via GitOps.

Here's how pingali can do this via GitOps: https://github.com/fleetdm/fleet/pull/31991

Docs here: https://fleetdm.com/docs/configuration/yaml-files#end-user-license-agreement

Up to you on whether to close this request as done or leave it open with feedback.

[noahtalerman]

FYI @Patagonia121 we just found a bug with the feature: https://github.com/fleetdm/fleet/issues/32016

The feature works. pingali just has to use a path starting from the root of the directory instead of the relative path to the EULA until we fix the bug.