Support gateway-only deployments behind AWS HTTPS proxies - #1032
Open
ReganBell wants to merge 8 commits into
Open
Support gateway-only deployments behind AWS HTTPS proxies#1032ReganBell wants to merge 8 commits into
ReganBell wants to merge 8 commits into
Conversation
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
ReganBell
marked this pull request as ready for review
September 9, 2026 23:02
Co-authored-by: Codex <codex@openai.com>
ReganBell
changed the title
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.
A deployment using only a model gateway key and an HTTPS proxy in front of an HTTP AWS ALB cannot complete its first live session: Pi checks direct provider credentials before the gateway adapter runs, and the CLI attempts to deliver its sandbox package directly to the ALB over TLS.
This change resolves authentication for mapped models without registering a provider-wide gateway credential, routes signed layer requests through the configured HTTPS front door for HTTP origins, and forwards the required signature/capability headers in the AWS scaffold. Direct ALB TLS binding remains unchanged. Conformance now parses only tool.json descriptors, allowing tools to include executable and JSON installation assets.
Validation: gateway-only failure reproduced with a real AgentSession against a local HTTP streaming endpoint; 50 focused model tests, 54 deployment-layer/template tests, 114 AWS tests (including four focused transport tests), core and CLI typechecks, and focused lint pass. Independent review covered credential isolation, user-provider overrides, stale mappings, preserved model headers, TLS and redirect behavior, and installation assets. Live AWS validation is pending this exact candidate.