e2e: identify the target actor with the ate-target-actor header - #35
Closed
keithmattix wants to merge 1 commit into
Closed
e2e: identify the target actor with the ate-target-actor header#35keithmattix wants to merge 1 commit into
keithmattix wants to merge 1 commit into
Conversation
The pinned agentgateway nightly resolves the ingress target from the ate-target-actor header (<atespace>/<actor>) and no longer falls back to the Host/:authority, so every Host-routed call in the e2e suites now gets a 404 from the dataplane. Port the calling convention: add the shared internal/atenet header contract and send the header from the router client (requests and CONNECT), the demo callers, and the gRPC, websocket, and arbitrary-port ingress tests.
Collaborator
Author
|
AI did this; we need an upstream substrate sync instead |
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.
The pinned agentgateway nightly (
v0.0.0-alpha.988ac151) resolves the ingress target from theate-target-actorheader (<atespace>/<actor>) and no longer falls back to the Host/:authority, so every Host-routed call in the e2e suites gets a 404 from the dataplane — this is what failed bothpr-workflowandhelm-e2eon the #28 squash (971d345).Port the calling convention from the upstream agentgateway integration branch: add the shared
internal/atenetheader contract and send the header from the router client (plain requests and CONNECT), the demo suite callers, and the gRPC, websocket, and arbitrary-port ingress tests.