Palantir DevOps Environment Separation

Overview

Represent long-lived environments with Foundry spaces and promote versioned products through DevOps and Marketplace. Use Global Branching for isolated changes within an environment, not as a substitute for every long-lived environment boundary.

Prerequisites

• Identify the enrollment, DevOps store, source products, target spaces, owners, dependencies, security policies, external systems, and approval chain.
• Inventory environment-specific sources, sinks, URLs, OAuth clients, markings, organizations, schedules, and release windows.
• Read references/official-docs.md and inspect the current product dependency and parameter contracts.
• Establish the development source product and at least one non-production installation.

Current Contract

• Spaces provide environment separation for development, test, and production workflows.
• DevOps products package resources and their dependencies; downstream products should resolve inputs from the corresponding target environment.
• Marketplace installations can use release channels, locks, maintenance windows, and parameter inputs.
• Supported Developer Console application parameters can be remapped during installation, but Ontology API-name behavior and source-code parameters need explicit review.