Agent skill · software engineering · jeremylongshore
glean-deploy-integration
Deploy Glean custom connectors as scheduled jobs on Cloud Run, Lambda,
Why this skill is useful
Adds a complete Docker deployment script for Glean custom connectors, including health checks and error handling that aren't in public docs.
What it needs
Requires docker 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 Deploy Integration Overview Deploy a containerized Glean enterprise search integration service with Docker. This skill covers building a production image that connects to Glean's Indexing and Search APIs for managing document ingestion, custom datasource connectors, and search queries. Includes environment configuration for multi-datasource indexing, health checks that verify API connectivity and indexing status, and rolling update strategies that avoid interrupting active indexing jobs. Docker Configuration Environment Variables Health Check Endpoint Deployment Steps Step 1: Build Step 2: Run Step 3: Verify Step 4: Rolling Update Error Handling Issue Cause Fix ------- ------- ----- 401 Unauthorized Invalid indexing token Regenerate token in Glean admin under Custom Connectors 403 Forbidden Datasource not registered Create datasource in Glean admin before indexing 400 Bad Request Malformed document payload Validate document schema against Glean Indexing API spec 429 Rate Limited Exceeding indexing rate limits Batch documents (max 100 per request) and add backoff Stale search results Connector not running on schedule Verify cron schedule or Cloud Scheduler job status Prerequisites An approved deployment change, environment-specific secret references, and a destination allowlist that distinguishes sandbox, staging, and production. Health, freshness, and synthetic allow/deny baselines plus a tested rollback artifact. A canary datasource that carries only approved data and has a named owner. Instructions 1. Build and test the immutable artifact with mocked or sandbox fixtures; refuse literal credentials and unknown destinations. 2. Deploy to staging, verify health, bounded index behavior, freshness, and both authorization probes before requesting production approval. 3. Release first to the canary datasource with concurrency and retry caps, monitoring errors and redacted correlation IDs. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/glean-deploy-integration