Skip to content

Run the networking e2e tests for sdsmint variant - #1155

Draft
haiyanmeng wants to merge 1 commit into
agent-substrate:mainfrom
haiyanmeng:enable-networking-e2e-test-sdsmint
Draft

Run the networking e2e tests for sdsmint variant#1155
haiyanmeng wants to merge 1 commit into
agent-substrate:mainfrom
haiyanmeng:enable-networking-e2e-test-sdsmint

Conversation

@haiyanmeng

@haiyanmeng haiyanmeng commented Aug 23, 2026

Copy link
Copy Markdown
Collaborator

Fixes #<issue_number_goes_here>

https://github.com/agent-substrate/substrate/actions/runs/32672505026/job/97280361219?pr=1155 shows the time overhead of these new steps.

It's a good idea to open an issue first for discussion.

  • Tests pass
  • Appropriate changes to documentation are included in the PR

@haiyanmeng
haiyanmeng marked this pull request as draft August 23, 2026 20:38
@haiyanmeng
haiyanmeng force-pushed the enable-networking-e2e-test-sdsmint branch from 7220c90 to 4db255e Compare August 23, 2026 21:45
Run the networking suite a second time against the sdsmint (MITM)
egress gateway, so the egress path is covered on both gateway variants
rather than only on passthrough.

The suite's egress tests cannot reuse the plain egress demo there:
under sdsmint the origin certificate TestActorEgressHTTPS sees is a
per-SNI leaf the gateway minted, which chains to no public CA, so the
demo's stock system roots fail the handshake. Add egress-mitm and
egress-microvm-mitm, siblings of the two egress demos that project the
egress gateway trust bundle and set SSL_CERT_FILE/SSL_CERT_DIR at it so
their anchor set is exactly the gateway CA.

These are their own fixtures rather than a change to the egress demos:
the bundle only resolves on an sdsmint install, and an actor
referencing a bundle that does not resolve never starts, so folding it
into the shared templates would break every passthrough install.
Registering them as demos gets them into --help and delete_all's
teardown sweep for free.

The suite picks between the two pairs on E2E_EGRESS_MITM, the same knob
the egressmitm suite gates on -- the gateway is a cluster-wide choice
the suite cannot infer from its fixtures. CI sets it on the networking
step that runs after the sdsmint gateway is deployed, and deploys the
matching fixture there.

https://github.com/agent-substrate/substrate/actions/runs/32665044490/job/97262716880
@haiyanmeng
haiyanmeng force-pushed the enable-networking-e2e-test-sdsmint branch from 4db255e to 048e7f1 Compare August 23, 2026 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant