Loading
chore(datastore): add the container upstream write statements part 3/15 (S17 Phase 6 plan: 42/42)
Why
The go-jet builders the writes run, plus the two rules that gate an association before any of them: the positive format-family admission and the list predicate that refuses a duplicate before the cap.
maxContainerVirtualUpstreams lives in container_virtual_resolution.go, and this part is where a write path starts enforcing it, so that file's claim that no write path does is corrected here.
The stack
Fifteen parts, each stacked on the last, each green on its own, reviewed in this order. Changed lines counts added plus deleted.
The delete guard in part 9 lands before the routes in part 11, so no window exists where a container association is writable without the refusal that protects it.
Related to #314 (closed)
Edited by Hayley Swimelar