glean-multi-env-setup
Use separate datasource names per environment (wiki_staging vs wiki_prod). '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill glean-multi-env-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ```t
- Overview
- Environment Configuration
- Environment Files
- Environment Validation
- Promotion Workflow
- Environment Matrix
- Error Handling
- Resources
- Next Steps
curl -X POST "$GLEAN_BASE_URL/indexing/datasources/wiki_sandbox/documents" \ curl "$GLEAN_BASE_URL/search" -H "Authorization: Bearer $GLEAN_API_TOKEN_STG" \ node scripts/compare-search-quality.js --env staging --baseline baseline.json cp connectors/staging/*.json connectors/production/ curl -X POST "$GLEAN_BASE_URL/indexing/datasources/wiki_prod/crawl" \
What does the glean-multi-env-setup skill do?
Use separate datasource names per environment (wiki_staging vs wiki_prod). '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill glean-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.