mirror of
https://github.com/fleetdm/fleet
synced 2026-04-21 13:37:30 +00:00
550de39a7c
#22555 This resolves issues where no-team script paths are resolved relative to the base rather than the file they're in. There was a similar issue for software packages, which I also fixed. This also fixes script-poolicy associations when scripts and policy files automating those scripts need different relative paths. Test file moves ensure that these fixes are tested. # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] Added/updated tests - [x] Manual QA for all new/changed functionality
1 line
No EOL
288 B
Text
1 line
No EOL
288 B
Text
* GitOps script and software installer relative paths are now always relative to the file they're in. This change breaks existing YAML files that had to account for previous inconsistent behavior (e.g. script paths declared in no-team.yml being relative to default.yaml one directory up). |