feat(gcp-cloud-run): support plan protocol v2#2790
Open
jrusso1020 wants to merge 1 commit into
Open
Conversation
This was referenced Jul 25, 2026
Collaborator
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
jrusso1020
force-pushed
the
feat/plan-protocol-v2-gcp
branch
5 times, most recently
from
July 25, 2026 21:46
d527c47 to
d22ec30
Compare
jrusso1020
marked this pull request as ready for review
July 25, 2026 22:00
jrusso1020
force-pushed
the
feat/plan-protocol-v2-gcp
branch
from
July 25, 2026 22:02
d22ec30 to
dfd3881
Compare
jrusso1020
force-pushed
the
feat/plan-protocol-v2-gcp
branch
from
July 25, 2026 22:34
dfd3881 to
5fc20bd
Compare
jrusso1020
force-pushed
the
feat/plan-protocol-v2-aws
branch
from
July 25, 2026 22:35
ae9fbad to
2ff3705
Compare
7 tasks
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
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.

Summary
Stack
Safety
plan call gets the longer IAM-propagation horizon, while chunk/assemble keep
their original retry count
Validation
Live GCP gate
Environment:
hyperframes-dev,us-east1, owner hash1315a5c6e8.The first live attempt exposed Cloud Run IAM propagation longer than the
original retry horizon. The final run exercised a newly-created private
service and workflow from cold state:
SUCCEEDED, 114,236 ms, 37.40 dB PSNRSUCCEEDED, 12,059 ms, 37.40 dB PSNRfe3bf65710fd0a362901dbecdfc50f22f5c4d974cbf7723365ad133cb65c929dNO_AUDIOfixture)ac64dc35c1cfb59e7c8aaddad900e15d406d9e9ae465a437e45c09a99fe4dedfAutomatic cleanup passed for the successful run. A separate read-only audit
checked Cloud Run, Workflows, both service accounts, render/build buckets,
Artifact Registry repositories, and image packages for the successful and
earlier failed owner hashes (
1315a5c6e8,ac116fa597,4926f2dcc6,590d3dd8f2): 32/32 resources were absent.Evidence is retained locally under
examples/gcp-cloud-run/scripts/gcp-smoke-artifacts/1315a5c6e8/; GCP retainsonly Cloud Build and Cloud Logging/audit history.