Salesforce-Connected Application Deployment

Overview

Release customer-owned adapter code independently of Salesforce metadata while proving the target org, secrets, API contract, and business invariants.

Prerequisites

• Immutable application artifact, source commit, dependency lock, SBOM or equivalent inventory, and deployment target
• Approved Salesforce app and principal, target-org identity, supported API contract, and secret references
• Preview environment, canary, health and business checks, capacity budget, rollback, and incident owners

Tool Discipline

Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts.

Current Contract

A Salesforce-connected application may run on many compute platforms; Salesforce does not define one universal deployment target. The application must bind to the customer-approved org, OAuth app, API version, limits, schema, and event contract.