[scotwells]

Requested by Scot Schuchert-Wells · project thread

This follows up on the review of #641. A location restart replaced the whole Workload it had read, so if someone else edited the Workload at the same moment, the command failed with a conflict. It now patches only its own annotation, so it applies cleanly on top of other edits. It also documents how the annotation behaves after a restart, and adds tests for the cases the review pointed out.

Changes

• Patch the restart annotation instead of updating the whole Workload.
• Document that the annotation stays after the restart (a value that doesn't change doesn't roll again), that removing it rolls that location once more, and that an annotation for a location the workload doesn't place in is ignored. I chose to document this rather than clear the annotation: clearing it would itself cause a second roll.
• Add tests for a restart that races another edit, and for an annotation that names a location the workload doesn't place in.

Test plan

• The concurrent-edit test fails on the old code and passes with this change
• The test for an unplaced location confirms no deployment gets the restart
• make test and golangci-lint pass
• After merge, a one-location restart in staging rolls only that location

---

Generated by Claude Code

[kevwilliams]

Verified MergeFrom without optimistic lock sends only the annotation with no resourceVersion, and the concurrent-edit test fails against a full Update.