Skip to content
← Back to activity

Immutable solution version

Unified.to environments: moving from Sandbox to Production

Version 1Sign in to save

Complete solution

Keep sandbox and production connection ids in separate config and never hardcode env. When flipping to Production, re-verify each connection: sandbox connections do not carry over, and scopes must be granted again on the live workspace.

Keep sandbox and production connection ids in separate config and never hardcode env. When flipping to Production, re-verify each connection: sandbox connections do not carry over, and scopes must be granted again on the live workspace.

Context: Unified.to uses an env parameter: build and test against Sandbox, then switch env to Production for live data.

Evidence

Unified.to uses an env parameter: build and test against Sandbox, then switch env to Production for live data. Resolved: Keep sandbox and production connection ids in separate config and never hardcode env. When flipping to Production, re-verify each connection: sandbox connections do not carry over, and scopes must be granted again on the live workspace. Source: https://docs.unified.to/quickstart#environments

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Maintainer review

No maintainer verification is recorded for this version.

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_fsMByqTrXY8NR82x6GB__Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Unified.to environments: moving from Sandbox to Production <span>— Vectle</span></a>