shrutiyam-glitch 6a35150e29 Remove onResume.fromData and the DATA_ON_GOLDEN restore scope (#2105) ...

Fixes #2027 

Actor lifecycle v2 will not restore an actor by combining the golden
snapshot's guest state with the actor's own data snapshot.
`onResume.fromData: GOLDEN` was the only way into that path, so this
removes the setting and everything behind it.

#### Behavior changes
- **API:** an ActorTemplate that sets `snapshotConfig.onResume` is
rejected (unknown field). Templates already stored lose the field
silently on read.
- **Resume of a DATA snapshot** always starts the containers fresh from
the image, with the durable dirs filled from the snapshot. Templates
that used `fromData: GOLDEN` now pay app startup on resume and lose any
in-memory state that came from the golden image.
- **Unchanged:** FULL snapshots, a just-created actor (borrows the
golden tag and restores it FULL, or cold-boots via `Run` if there is
none), committing the golden actor (always FULL), and creating actors
from a tag.
- **Restore path:** a DATA_ON_GOLDEN restore used to need two manifest
GETs and downloads from two snapshots; every restore now reads one
manifest and one snapshot.
- **Metrics:** `ate.snapshot.scope` takes only `full`, `data` or
`unknown`.
- **Rollout:** atelet rejects scope 3, so upgrade ateapi and atelet
together. Per the pre-v1.0 policy there is no compatibility shim.

**This is a Breaking change**




- [ ] Tests pass
- [ ] Appropriate changes to documentation are included in the PR

2026-10-02 05:08:42 +00:00

..

api/v1alpha1

microvm: drop the kata-config asset (#1704)

2026-09-22 00:18:59 +00:00

client

Drop k8s third_party deps now that HEAD is updated (#1480)

2026-09-04 17:02:12 -07:00

objectstorage

ategcs: rename and move to pkg/ for reuse outside atelet (#2013)

2026-10-01 01:29:23 +00:00

proto

Remove onResume.fromData and the DATA_ON_GOLDEN restore scope (#2105)

2026-10-02 05:08:42 +00:00