Agent skill · software engineering · jeremylongshore
glean-multi-env-setup
Use separate datasource names per environment (wiki_staging vs wiki_prod).
Why this skill is useful
Adds specific environment configuration patterns and validation scripts for Glean that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq installed locally. Requires glean account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 Environment Files Environment Validation Promotion Workflow Environment Matrix Setting Dev (Sandbox) Staging Prod --------- --------------- --------- ------ Data Source Synthetic test docs Subset of real docs Full document index Datasource Suffix sandbox staging prod Connectors Mock connectors Real connectors Real connectors User Access Developers only QA + developers All employees Crawl Frequency Manual Daily Continuous Error Handling Issue Cause Fix ------- ------- ----- Datasource not found Suffix mismatch between env and config Verify GLEANDATASOURCESUFFIX matches connector registration 401 on indexing API Token scoped to wrong instance Regenerate token in the correct Glean admin console Search returns stale results Crawl not triggered after promotion Manually trigger crawl via indexing API Connector sync fails OAuth credentials expired for data source Re-authorize connector in Glean admin for the target env Staging indexes prod data Connector config copied without suffix update Always update datasource names when promoting configs Prerequisites Distinct credentials, opaque datasource names, and network destinations for sandbox, staging, and production. A secret-manager reference per environment, protected promotion approval, and a documented production rollback revision. Synthetic fixtures for sandbox and an owner-approved minimized staging sample; never copy production credentials or unrestricted documents into CI. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/glean-multi-env-setup