fleet/pkg/spec/testdata/policies/script-policy.yml

- name: 🔥 Failing policy with script
  platform: linux
  description: This policy should always fail.
  resolution: There is no resolution for this policy.
  query: SELECT 1 FROM osquery_info WHERE start_time < 0;
  run_script:
    path: ../lib/collect-fleetd-logs.sh
Backend build for script automation (#22472) #22115, #22116 # 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. --> No changes file, as FE changes file covers the entire feature - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [x] Added/updated tests - [x] If database migrations are included, checked table schema to confirm autoupdate - For database migrations: - [x] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [x] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [x] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). - [x] Manual QA for all new/changed functionality --------- Co-authored-by: Jacob Shandling <jacob@fleetdm.com> Co-authored-by: Tim Lee <timlee@fleetdm.com> 2024-10-04 01:03:40 +00:00			`- name: 🔥 Failing policy with script`
			`platform: linux`
			`description: This policy should always fail.`
			`resolution: There is no resolution for this policy.`
			`query: SELECT 1 FROM osquery_info WHERE start_time < 0;`
			`run_script:`
Switch path resolution for scripts to happen when spec is parsed (#22782) #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 2024-10-09 22:57:08 +00:00			`path: ../lib/collect-fleetd-logs.sh`