[DRAFT] feat(harness): reconcile execution role policies - #1991
Closed
aidandaly24 wants to merge 1 commit into
Closed
[DRAFT] feat(harness): reconcile execution role policies#1991aidandaly24 wants to merge 1 commit into
aidandaly24 wants to merge 1 commit into
Conversation
aidandaly24
had a problem deploying
to
e2e-testing
August 13, 2026 13:17 — with
GitHub Actions
Failure
Contributor
Author
|
Withdrawing this draft stack for scope and architecture reduction before review. |
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
--execution-role-arn, unknown roles, deterministic cross-resource ownership, and--skip-role-policy-updateStack
Depends on #1990.
Verification
bun run format:checkbun run lint:checkbun run typecheckbun test: 1238 passed, 0 failedbun run buildAWS_PROFILE=deploycreate/update/invoke/delete coverage for managed Memory, Browser, Code Interpreter, AWS IAM and no-auth Gateways, API-key-backed remote MCP, explicit roles, skipped IAM, unknown roles, failed-update rollback, and generated-policy cleanup