Adobe Versioned Adapter Patterns

Overview

Create narrow, version-pinned Adobe SDK and REST adapters with typed contracts, redaction, bounded polling, and compatibility evidence. This workflow produces a reviewable artifact and evidence before any live side effect.

Prerequisites

• Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle.
• Named product, identity, security, data, budget, release, and operations owners appropriate to the scope.
• Synthetic or approved non-production fixtures with secret and content canaries.

Current Contract

SDK package versions and REST product versions change independently. Keep auth, transport, schema validation, returned status URLs, request identifiers, storage custody, and retry classification behind service-specific interfaces. The retired Lightroom Firefly Services SDK is excluded. Recheck the dated evidence map before relying on mutable product behavior.

Authentication

Inject a credential provider; never let callers pass raw secrets. Bind every client to environment, organization/project, service, scopes, product profiles, and redaction policy.