brightdata-prod-checklist

name	brightdata-prod-checklist
description	Execute Bright Data production deployment checklist and rollback procedures. Use when deploying Bright Data integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "brightdata production", "deploy brightdata", "brightdata go-live", "brightdata launch checklist".
allowed-tools	Read, Bash(kubectl:*), Bash(curl:*), Grep
version	1.0.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","scraping","data","brightdata"]
compatible-with	claude-code

Bright Data Production Checklist

Overview

Complete checklist for deploying Bright Data scraping integrations to production with zone verification, monitoring, and rollback procedures.

Prerequisites

• Staging environment tested
• Production zone credentials in secrets vault
• Monitoring and alerting configured

Instructions

Step 1: Zone and Credential Verification

• Production zone active in Bright Data CP
• Zone password stored in secrets vault (not .env)
• API token scoped to production zone only
• SSL certificate (brd-ca.crt) deployed
• Separate zone from development/staging

# Verify production zone is active
curl -s -H "Authorization: Bearer ${BRIGHTDATA_API_TOKEN}" \
  https://api.brightdata.com/zone/get_active_zones \
  | python3 -c "import sys,json; zones=json.load(sys.stdin); print([z['name'] for z in zones])"

# Test production proxy connectivity
curl -x "http://brd-customer-${BRIGHTDATA_CUSTOMER_ID}-zone-${BRIGHTDATA_ZONE}:${BRIGHTDATA_ZONE_PASSWORD}@brd.superproxy.io:33335" \
  -s -w "HTTP %{http_code} in %{time_total}s\n" \
  https://lumtest.com/myip.json

Step 2: Code Quality

• No hardcoded credentials (grep for passwords, tokens)
• Retry logic with exponential backoff (see brightdata-rate-limits)
• Request queuing with concurrency limits (p-queue)
• Response validation (check for CAPTCHA pages, empty responses)
• Timeout set to 60-120s for Web Unlocker
• Error logging includes headers