Project UX Updated Around Environments

Projects now center around project environments as the primary way to configure and understand deployments.

With the move to a one-to-one relationship between project environments and deployment configuration, the Project experience has been updated to make environments the main entry point for deployment settings and resource architecture visibility.

Each environment now represents its own deployment configuration, replacing the previous model based on named deployment policies.

What’s new

• Projects now reflect a one-to-one relationship between environments and deployment configuration
• The environment of type development is the default selected environment.
• Deployment settings are configured directly on project environments
• Named deployment policies are no longer the primary configuration surface. The project environment name or alternateId is.
• If a project environment is deployed, a resource architecture diagram for the selected environment is displayed, otherwise an option to set up the deployment is displayed
• Environment selection now determines the infrastructure view and settings shown

Why this matters

This update makes deployment configuration easier to understand by aligning infrastructure settings with the environments they affect.

• Clearer mental model for how deployments are structured
• Environment-specific infrastructure visibility
• Simpler navigation between development, production, and other custom environment setups
• Fewer indirections when configuring deployment behavior

Things to know

• Deployment configuration now lives on project environments
• Resource architecture diagrams reflect the selected environment
• Each environment represents a single deployment configuration
• Named deployment policies have been replaced by environment-based configuration