Skip to content

refactor: validate runtime fault network choices - #41

Merged
0xcadams merged 1 commit into
0xcadams/type-client-certificate-phasefrom
0xcadams/type-runtime-network
Oct 1, 2026
Merged

0xcadams merged 1 commit into
0xcadams/type-client-certificate-phasefrom
0xcadams/type-runtime-network

Conversation

@0xcadams

@0xcadams 0xcadams commented Oct 1, 2026

Copy link
Copy Markdown
Member

What

Parse the runtime-load scenario and network impairment path into finite TypeScript choices before fault orchestration.

Why

Runtime fault scenarios already had a Zod enum, but setup used raw SCENARIO and NETWORK_PATH environment strings and passed a loose path into the fault runtime. That left typing behind at the entry point.

Changes

  • Derive NetworkPath from its Zod schema and parse environment input before constructing the typed fault runtime.
  • Parse the combined internal and external runtime scenarios once while retaining the existing fault event schema.
  • Exercise both valid paths and invalid or missing path input without changing the impairment command sequence.

@0xcadams
0xcadams force-pushed the 0xcadams/type-runtime-network branch from ee39620 to 5bfe6d4 Compare October 1, 2026 06:02
@0xcadams
0xcadams changed the base branch from main to 0xcadams/type-client-certificate-phase October 1, 2026 06:03
@0xcadams
0xcadams added this pull request to stack #43 October 1, 2026 06:03
@0xcadams
0xcadams force-pushed the 0xcadams/type-runtime-network branch from 5bfe6d4 to e0145fd Compare October 1, 2026 06:30
@0xcadams
0xcadams merged commit 5f21f61 into main Oct 1, 2026
23 checks passed
@0xcadams
0xcadams deleted the 0xcadams/type-runtime-network branch October 1, 2026 06:50
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