Custom Environment support is now live! You can create, delete, rename and reorder environments to match your team's preferred workflow and tailor your own secret management setup.
Organize secrets with Environments
Phase Apps come batteries-included, with Development, Staging and Production environments. These allow you to keep secrets used for development or pre-production pipelines separate from secrets used in production. This is a central tenet of secret management, and allows for users and machines to get access to only the secrets they need.
However, not every team's structure or workflow is likely to align with this 3-environment setup. You may need a separate "Testing" environment for running test suites, a "Preview" environment for generating preview builds, a complex build and deployment pipeline that requires a dozen different environments, or perhaps you keep it simple with just "Development" and "Production". Regardless of how you choose to build and deploy your code, your secret management solution should be tailored to fit.
Custom Environments gives you the flexibility to create and manage environments to reduce developer friction, maintain least-privilege access to secrets, while still providing a central place for your team to develop, manage and deploy secrets.
Creating a Custom Environment
To create a new Environment, simply click on the "New Environment" button on the Secrets tab in your App. Enter a descriptive name and click Create.
You can make sure your environments appear in the correct order across the Console by clicking the 'Swap' button on the bottom of each Environment card to swap them with the adjacent Environment.
Managing Custom Environments
Click the "Manage" button on any Environment to rename the Environment, manage user access, or delete it.
CLI Support
To work with custom environments from the CLI, simply pass the --env flag to any command:
Custom Environments are live on Phase Cloud, and available in Phase Console v2.29.0 for users running Phase self-hosted.
Reach out on Slack or GitHub for any questions or feedback on this release!