mirror of
https://github.com/fleetdm/fleet
synced 2026-05-19 06:58:30 +00:00
e470a1ea22
relates to [#28691](https://github.com/fleetdm/fleet/issues/28691) This adds the ability to upload the EULA users see during the setup experience via gitops. It follows patterns used for uploading the bootstrap package via gitops. I've also added a sha256 column to the `eulas` table in order to easily compare the existing eula with a new one to see if we need to perform an upload. Finally I added the support to generate this new gitops setting with the `generate-gitops` command - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. - [x] If database migrations are included, checked table schema to confirm autoupdate - For new Fleet configuration settings - [x] Verified that the setting can be managed via GitOps, or confirmed that the setting is explicitly being excluded from GitOps. If managing via Gitops: - [x] Verified that the setting is exported via `fleetctl generate-gitops` - [x] Added the setting to [the GitOps documentation](https://github.com/fleetdm/fleet/blob/main/docs/Configuration/yaml-files.md#L485) - [x] Verified that the setting is cleared on the server if it is not supplied in a YAML file (or that it is documented as being optional) - [x] Verified that any relevant UI is disabled when GitOps mode is enabled - For database migrations: - [x] Added/updated automated tests - [x] Manual QA for all new/changed functionality |
||
|---|---|---|
| .. | ||
| cached_mysql | ||
| filesystem | ||
| mysql | ||
| mysqlredis | ||
| redis | ||
| s3 | ||