| name | adobe-deploy-integration |
| description | Deploy Adobe-powered applications to Vercel, Cloud Run, and Adobe App Builder
with proper credential injection and health monitoring.
Use when deploying Adobe API integrations to production platforms.
Trigger with phrases like "deploy adobe", "adobe Vercel",
"adobe Cloud Run", "adobe App Builder deploy", "adobe production deploy".
|
| allowed-tools | Read, Write, Edit, Bash(vercel:*), Bash(gcloud:*), Bash(aio:*) |
| version | 1.7.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","design","adobe"] |
| compatibility | Designed for Claude Code |
Adobe Deploy Integration
Overview
Deploy Adobe-powered applications to three platforms: Vercel (serverless), Google Cloud Run (containers), and Adobe App Builder (native Adobe Runtime). Each with proper OAuth credential management.
Prerequisites
- Adobe OAuth Server-to-Server credentials for production
- Platform CLI installed (
vercel, gcloud, or aio)
- Application tested in staging environment
Instructions
Option A: Adobe App Builder (Native Adobe Hosting)
App Builder deploys serverless Runtime actions directly to Adobe infrastructure:
# Login to Adobe I/O CLI (requires IMS auth since AIO CLI v11)
aio login
# Select your project and workspace
aio console project select
aio console workspace select Production
# Deploy all actions, static assets, and event registrations
aio app deploy
# Check deployed actions
aio runtime action list
# View action logs
aio runtime activation list --limit 10
aio runtime activation logs <activationId>
// app.config.yaml — App Builder configuration
application:
actions: actions
web: web-src
runtimeManifest:
packages:
my-adobe-app:
actions:
process-image:
function: actions/process-image/index.js
runtime: nodejs:20
inputs:
ADOBE_CLIENT_ID: $ADOBE_CLIENT_ID
ADOBE_CLIENT_SECRET: $ADOBE_CLIENT_SECRET
annotations:
require-adobe-auth: true
final:
