Project Environment Types and One-to-One Deployment Policies

Project environments now have clearer roles and a simpler deployment model.

You can now assign a type to each project environment and map exactly one deployment policy to each environment. Deployment policies are now environment-specific, replacing the previous model where a single policy could target multiple environments.

Each environment now acts as the primary anchor for its deployment configuration, making infrastructure behavior more predictable across development and production workflows.

What’s new

• Assign environment types: development, production, or custom
• Only one development environment is allowed per project
• Only one production environment is allowed per project
• Each environment now maps to exactly one deployment policy
• Deployment policies can no longer target multiple environments
• Deployments are now directly associated with their project environment

Why this matters

Environments now represent distinct lifecycle stages with dedicated infrastructure behavior. One-to-one policy mapping removes ambiguity and makes deployments easier to reason about across teams and projects.

• Clearer separation between development and production infrastructure
• Predictable deployment behavior per environment
• Simpler deployment configuration model
• Stronger foundation for environment-aware automation and scaling

Things to know

• Every project environment now includes a required type
• development and production environments must be unique within a project
• Each environment is associated with exactly one deployment policy
• Deployment policies are no longer shared across multiple environments
• Deployments are now anchored to a single project environment
• Custom environments remain available for specialized workflows