Skip to content

Tidy wizard env vars: WIZARD_ prefix, ignore in prod builds#603

Open
gewenyu99 wants to merge 2 commits into
mainfrom
fix/tidy-env-var
Open

Tidy wizard env vars: WIZARD_ prefix, ignore in prod builds#603
gewenyu99 wants to merge 2 commits into
mainfrom
fix/tidy-env-var

Conversation

@gewenyu99

Copy link
Copy Markdown
Collaborator

Problem

Changes

Test plan

Replace the greedy yargs .env('POSTHOG_WIZARD') prefix with explicit per-option WIZARD_* defaults, gated to dev/CI builds. The bare prefix would have claimed the whole WIZARD_* namespace under strictOptions and rejected unrelated vars (the build's own WIZARD_BUILD_NODE_ENV, the workbench's WIZARD_PATH/REF/...), breaking parsing; explicit wiring reads only the names we declare.

Rename POSTHOG_WIZARD_* -> WIZARD_* and consolidate the duplicate API-key path (POSTHOG_PERSONAL_API_KEY) into WIZARD_API_KEY. All these vars are ignored in published builds (IS_PRODUCTION_BUILD); end users drive the CLI through flags. Drop the dead POSTHOG_API_KEY allowlist entry and null it in the agent/MCP subprocess env so a stray shell key can't reach them. Update README, tests, and smoke-test CI.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copy link
Copy Markdown
Collaborator Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

# Conflicts:
#	README.md
#	src/commands/basic-integration/index.ts
#	src/lib/runners/run-wizard.ts
@gewenyu99 gewenyu99 marked this pull request as ready for review June 16, 2026 03:09
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