notion-multi-env-setup

# Notion Multi-Environment Setup ## Overview Configure separate Notion integrations for development, staging, and production. Each environment uses its own integration token, targets different databases, and applies environment-appropriate log levels and timeouts. This prevents dev data leaking into prod, isolates testing, and enforces least-privilege per tier. ## Prerequisites - Notion workspace(s) per environment (one workspace can serve dev/staging via separate integrations) - `@notionhq/client` v2+ installed (`npm install @notionhq/client`) - Python alternative: `notion-client` (`pip install notion-client`) - Secret management platform (AWS Secrets Manager, GCP Secret Manager, or HashiCorp Vault) - CI/CD pipeline with per-environment variable injection ## Instructions ### Step 1: Create Per-Environment Integrations and Env-Aware Client Create separate integrations at https://www.notion.so/my-integrations with scoped capabilities: | Environment | Integration Name | Capabilities | Timeout | Log Level | |-------------|-----------------|--------------|---------|-----------| | Development | `my-app-dev` | All (read+update+insert+delete) | 60s | DEBUG | | Staging | `my-app-staging` | Read + Update + Insert | 30s | WARN | | Production | `my-app-prod` | Minimum required only | 30s | ERROR | **TypeScript — environment-aware client factory:** ```typescript import { Client, LogLevel } from '@notionhq/client'; interface NotionEnvConfig { token: string; databaseIds: Rec...