| name | adobe-multi-env-setup |
| description | Configure Adobe OAuth credentials and API access across development,
staging, and production environments with separate Developer Console
projects, secret managers, and environment-specific scoping.
Trigger with phrases like "adobe environments", "adobe staging",
"adobe dev prod", "adobe environment setup", "adobe config by env".
|
| allowed-tools | Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*) |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","design","adobe"] |
| compatibility | Designed for Claude Code |
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
interface AdobeEnvConfig {
imsEndpoint: string;
fireflyEndpoint: string;
photoshopEndpoint: string;
scopes: string;
retries: number;
timeoutMs: number;
cache: { enabled: ; : };
}
: <, > = {
: {
: ,
: ,
: ,
: ,
: ,
: ,
: { : , : },
},
: {
: ,
: ,
: ,
: ,
: ,
: ,
: { : , : },
},
: {
: ,
: ,
: ,
: ,
: ,
: ,
: { : , : },
},
};
(): & { : ; : } {
env = process.. || ;
config = configs[env] || configs.;
{
...config,
: process..!,
: process..!,
};
}