fix(infra): SF deploy 'Argument list too long' — pass definition via file:// (P0: live SFs stale)#371
Merged
Merged
Conversation
…(deploy broke) The Director SF state (2026-06-04) pushed the Saturday ASL to ~131 KB; the deploy-infrastructure.yml auto-deploy aborted at update-state-machine with "aws: Argument list too long" (exit 126) because the definition was passed inline via --definition "$(cat ...)". That silently left BOTH live state machines stamped behind origin/main HEAD → the deploy-drift preflight would halt the next weekday/Saturday pipeline run. Fix: --definition "file://$STAMPED" for both the Saturday + weekday updates. file:// reads from disk, so the bound is the SF service limit (1 MB), not the runner's ARG_MAX (env + args). No behavior change otherwise. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 5, 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.
P0 — main is in a half-deployed state; merging this self-heals it
The Director SF state (data #370) pushed the Saturday ASL to ~131 KB. The
deploy-infrastructure.ymlauto-deploy on the #370 merge (sha220094c) failed atupdate-state-machinewith:--definition "$(cat …)"passes the whole ASL inline; combined with the AWS session-token env on the runner it blew past the effectiveARG_MAX. Because the script aborted there (before the weekday update + CFN), both live state machines are still stamped at the previous main HEAD (956e7c6) whileorigin/mainis220094c— the deploy-drift preflight contract (live stamp == origin/main HEAD) is broken, so the next weekday/Saturday pipeline run could halt onDeployDriftCheck, and the Director state isn't live yet.Fix
--definition "file://$STAMPED"for both the Saturday + weekday updates.file://reads from disk → bounded by the SF service limit (1 MB), notARG_MAX. No other behavior change.Merging this self-heals
On merge,
deploy-infrastructure.ymlre-runs the fixed script: it restamps both live SFs to the new main HEAD, applies the Director state, and updates the CFN git-sha tag — closing the drift window. Please merge before the next weekday pipeline run (Fri 6 AM PT / 13:00 UTC) soDeployDriftCheckdoesn't halt trading.(I did not hand-apply
update-state-machinefrom this branch — per the merge-auto-deploy + drift-contract convention, the live SF must be stamped with a merged main SHA, not a branch SHA.)🤖 Generated with Claude Code