STATUS: D2.2a gates and merge recorded; deploy blockers re-pointed at aws-infra#56 - #246
Merged
Merged
Conversation
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.
D2.2a (#379) reached its tree-stage gates: engineering handoff, independent tester PASS, PM acceptance, merged to website main as 60a25617 plus the f2b32dd0 lint follow-up. The row stays in-progress until the development deploy is green.
The D0.1c and D1.2ca blocked reasons now name the real remaining blocker: the development terraform apply cannot run because the sandbox-account trust policy rejects the (now-correct) immutable OIDC subject; documented with evidence in aws-infra#56.