Use security.updates_at_first_boot, the name keel now asks for #4

Merged

marcos-mendez merged 1 commit from fix/spec-updates-rename into master

2026-09-26 18:08:37 -03:00

marcos-mendez commented

2026-09-26 17:59:29 -03:00

(Migrated from github.com)

keel deprecated security.updates on 2026-09-26: it reads as the machine's
update policy while it only ever controlled whether the first boot installs the
pending security updates. Every run of the boot test printed the deprecation
warning twice, once from keel spec apply and once from keel diff:

Warning: security.updates is deprecated, rename it to
security.updates_at_first_boot: ...

Renamed, with a comment saying what the field is. keel diff lists it as
not compared, so the value no longer needs the explanation the old name did,
and COVERAGE.md drops it from the list of values to revisit.

Test plan:

Rehearsed on keel-lxc-1 from a clean clone: boot test passes, 30 s for
the whole job, keel diff 6 same, 0 drift, 2 unknown, exit 13.
tests / coverage green here.

`keel` deprecated `security.updates` on 2026-09-26: it reads as the machine's update policy while it only ever controlled whether the first boot installs the pending security updates. Every run of the boot test printed the deprecation warning twice, once from `keel spec apply` and once from `keel diff`: Warning: security.updates is deprecated, rename it to security.updates_at_first_boot: ... Renamed, with a comment saying what the field is. `keel diff` lists it as `not compared`, so the value no longer needs the explanation the old name did, and `COVERAGE.md` drops it from the list of values to revisit. Test plan: - [x] Rehearsed on `keel-lxc-1` from a clean clone: boot test passes, 30 s for the whole job, `keel diff` 6 same, 0 drift, 2 unknown, exit 13. - [ ] `tests / coverage` green here.