Repository navigation
Distinguish serving traffic from latest-ready identity - #615
Merged
Merged
Conversation
This was referenced Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The latest-ready Cloud Run revision can be a no-traffic candidate, so ready/report equality alone does not establish which revision serves requests. Extend the existing read-only identity diagnostic with a separate projection of the status.traffic already returned by its one service read.
Only complete explicit distributions are compared. Output contains fixed single/split/absent/invalid status and three nullable booleans for report/configured positive traffic and report sole serving identity. Zero-percent tags do not serve; malformed or missing fields remain unknown without inferring from latestReady or tagged URLs. Revision names and other private metadata are never serialized.
The existing publisher guard, cloud calls, workflow, status/reasons and exit gate are unchanged. An exit-zero result still does not approve a serving identity, protected revision rotation or runtime recovery.
Validation: 30 additional regressions with the original 62 tests byte-preserved; 241 focused and 1,511 full-suite passes with 5 existing skips; Ruff and diff checks passed. All cloud/business inputs were mocked. Final CI and independent review are required before normal merge and a real read-only main inspection.
Related: QuantRuntimeSettings#632 and QuantRuntimeSettings#634.