adobe-multi-env-setup

# Adobe Multi-Environment Setup ## Overview Configure Adobe APIs across development, staging, and production environments using separate Developer Console projects, environment-specific OAuth credentials, and cloud-native secret management. ## Prerequisites - Adobe Developer Console access (admin or developer role) - Secret management solution (GCP Secret Manager, AWS Secrets Manager, or Vault) - CI/CD pipeline with environment variable injection ## Instructions ### Step 1: Create Separate Developer Console Projects Adobe best practice: one Developer Console **project** per environment with separate OAuth credentials. | Environment | Console Project | Scopes | Product Profile | |-------------|----------------|--------|-----------------| | Development | `my-app-dev` | `openid,AdobeID` | Dev sandbox | | Staging | `my-app-staging` | `openid,AdobeID,firefly_api` | Staging profile | | Production | `my-app-prod` | `openid,AdobeID,firefly_api,ff_apis` | Production profile | ### Step 2: Environment Configuration Files ```typescript // src/config/adobe.ts interface AdobeEnvConfig { imsEndpoint: string; // Same across all envs fireflyEndpoint: string; // Same across all envs photoshopEndpoint: string; // Same across all envs scopes: string; // Different per env (least privilege) retries: number; timeoutMs: number; cache: { enabled: boolean; ttlMs: number }; } const configs: Record<string, AdobeEnvConfig> = { development: { imsEndpoint: ...