joshsiv-mulga 4c3da1e346 test: add in-process integration test tier ...

Roughly half of the behavioural tests under tests/e2e/ assert control-plane
API shapes, authz and error codes that need no live environment, yet they can
only run against a tofu-provisioned environment on a scarce self-hosted
runner. This adds the tier they can move down to.

The real gateway router runs in-process: SetupRoutes() is a pure function of
GatewayConfig, so it serves from an httptest server over embedded NATS
JetStream with real IAM/STS services and genuine SigV4 verification. Only the
daemon side of the wire is faked -- the ec2.*/ebs.* NATS subjects a live node
would answer are stubbed per test.

Nothing is provisioned and no fixed ports are bound, so the tier runs
concurrently on a shared build host and is safe as a CI front gate ahead of
the live suites. It is build-tagged and kept out of preflight, which stays
unit-only.

2026-07-20 10:41:51 +10:00

..

describe_instances_test.go

test: add in-process integration test tier

2026-07-20 10:41:51 +10:00

harness.go

test: add in-process integration test tier

2026-07-20 10:41:51 +10:00

nats_stub.go

test: add in-process integration test tier

2026-07-20 10:41:51 +10:00