Execute Adobe production deployment checklist covering credential management,
SKILL.md
Adobe Production Checklist
Overview
Complete checklist for deploying Adobe API integrations to production, covering credential security, health monitoring, graceful degradation, and rollback procedures.
Prerequisites
Staging environment tested and verified
Production OAuth credentials created in Developer Console
Deployment pipeline with secret injection
Monitoring and alerting infrastructure ready
Instructions
Pre-Deployment: Credentials & Configuration
Production OAuth Server-to-Server credentials created (separate from staging)
ADOBE_CLIENT_ID and ADOBE_CLIENT_SECRET stored in secret manager (not env files)
Scopes are minimal: only APIs actually used in production
Token caching implemented (avoid re-generating per request)
I/O Events webhook endpoints use HTTPS with valid TLS cert
On-call team has adobe-incident-runbook accessible
Rollback Procedure
# Immediate rollback
kubectl rollout undo deployment/app
kubectl rollout status deployment/app
# Verify old version is healthy
curl -sf https://production.example.com/health | jq '.services.adobe'
Alert Configuration
Alert
Condition
Severity
Adobe Auth Failure
Any 401 errors
P1 — credential issue
Adobe Rate Limited
429 errors > 5/min
P2 — reduce throughput
Adobe API Down
503 errors > 10/min
P2 — enable fallback
Adobe High Latency
p99 > 10s
P3 — investigate
PDF Quota Low
< 50 transactions remaining
P3 — upgrade or throttle
Error Handling
Issue
Cause
Solution
401 after deploy
Wrong credentials for environment
Verify secret manager path
429 spike
Traffic increase from new feature
Add rate limiting queue
Health check flapping
Token caching not working
Check cache TTL logic
Webhook delivery stopped
Challenge response broken
Test webhook registration
Output
Following this guide produces the Adobe integration outcome for its topic—configuration, validation evidence, operational recovery, or a documented migration result. Record command output and relevant identifiers so a failed step is traceable.
Examples
Start with the smallest applicable command or code example already provided in this guide, using a non-production Adobe environment and credentials. Confirm the documented response or validation result before applying the pattern to production.