glean-multi-env-setup

# Glean Multi-Environment Setup ## Overview Glean enterprise search requires environment isolation to prevent test data from polluting production search results. Each environment uses its own datasource names, API tokens, and connector configurations. Sandbox indexes synthetic test documents, staging indexes a curated subset of real documents for search quality validation, and production indexes the full corpus. Connector changes must be tested in staging before promotion to avoid breaking search relevance for end users. ## Environment Configuration ```typescript const gleanConfig = (env: string) => ({ development: { apiToken: process.env.GLEAN_API_TOKEN_DEV!, baseUrl: "https://sandbox.glean.com/api/v1", datasourceSuffix: "_sandbox", indexingEnabled: true, searchQualityChecks: false, }, staging: { apiToken: process.env.GLEAN_API_TOKEN_STG!, baseUrl: "https://staging.glean.com/api/v1", datasourceSuffix: "_staging", indexingEnabled: true, searchQualityChecks: true, }, production: { apiToken: process.env.GLEAN_API_TOKEN_PROD!, baseUrl: "https://app.glean.com/api/v1", datasourceSuffix: "_prod", indexingEnabled: true, searchQualityChecks: false, }, }[env]); ``` ## Environment Files ```bash # Per-env files: .env.development, .env.staging, .env.production GLEAN_API_TOKEN_{DEV|STG|PROD}=<token> GLEAN_BASE_URL=https://{sandbox|staging|app}.glean.com/api/v1 GLEAN_DATASOURCE_SUFFIX={_sandbox|_staging|_prod} GLEAN_INSTANCE={sandbox|staging|produc...