Environment Configurations
Before you can deploy a pipeline in Salus, you need to configure an environment. Environments allow you to separate testing, staging, and production contexts, each with its own data sources, secrets, runtime settings, and access controls.
Environments
Environments in Salus are isolated contexts where pipelines are deployed and executed. Each environment has its own data connections, runtime settings, secrets, and access controls, allowing teams to safely test, stage, and run pipelines across different stages of development.
Think of environments as containers for running your pipelines under specific conditions, so that what happens in development doesn’t affect production.
Each environment also chooses its region when it’s created, so one organization can run environments across several regions and clouds at once.
By default, each workspace is provided with a single environment named Production.
Creating an environment and choosing its region
Environments and configurations
An environment is shared across a workspace; each project then gets its own configuration for that environment — the branch or tag it deploys, the compute it runs on, its variables and its networking. So “delete a configuration” and “delete an environment” are different acts, with very different blast radius.
In this section
- Configure an environment — region, deployment strategy, compute and networking.
- Environment variables — runtime and build-time values, secrets, files, and how they resolve.
- Manage and delete — change the deployment strategy, delete a configuration, delete an environment.