feat(cli): auto-detect environment variables as deploy secrets#2965
feat(cli): auto-detect environment variables as deploy secrets#2965
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Bundle Size ReportComparing against baseline from No bundle size changes detected. |
Unlighthouse Performance Comparison — VercelComparing PR preview deployment Unlighthouse scores vs production Unlighthouse scores. Summary ScoreAggregate score across all categories as reported by Unlighthouse.
Category Scores
Core Web Vitals
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Jira: TRAC-360
What/Why?
The deploy command now auto-detects required BigCommerce environment variables from
process.envwhen they aren't explicitly passed via--secret:BIGCOMMERCE_STORE_HASHBIGCOMMERCE_CHANNEL_IDBIGCOMMERCE_STOREFRONT_TOKENBIGCOMMERCE_API_HOSTBIGCOMMERCE_GRAPHQL_API_DOMAINThis pairs with the
--env-pathflag — instead of passing each variable individually as--secret KEY=VALUE, you can point to an env file and the deploy command will pick them up automatically:Missing required vars (
STORE_HASH,CHANNEL_ID,STOREFRONT_TOKEN) produce a warning. Optional vars (API_HOST,GRAPHQL_API_DOMAIN,AUTH_SECRET) are silently skipped. Explicit--secretflags always take precedence.Rollout/Rollback
Standard rollback — revert the commit. No migrations or feature flags involved.
Testing
Unit tests added covering:
process.env--secrettakes precedence (no duplicates)pnpm --filter @bigcommerce/catalyst exec vitest run src/cli/commands/deploy.spec.ts