Environments

Environments are isolated spaces for a single instance of an Application. They run on a designated Cluster and contain the Resources needed by the Application.

Locally, in Noop Workshop, Environments are used exactly as they are in the Cloud. Each Environment will have its own database and storage resources, as well as its own Secrets and Variables.

An Environment can be created manually from the Application dashboard or dynamically by a Pipeline or Runbook.

Configuration Using Runtime Variables and Secrets

Runtime Variables and Secrets can be used to configure environment variables accessible to an Application during its runtime. Runtime Variables are either defined in the Environment settings page in the Console or under the runtime key within a Blueprint Manifest (blueprint.yaml).

Runtime Secrets are defined exclusively in the Console. Runtime Secrets are encrypted by default within the Console and redacted from Environment logstreams.

In addition to user-defined Runtime Variables and Secrets, dynamic runtime variables can be used to create connections between Application Components and Resources.

See the Variables and Secrets guide for more usage details.

Deployments

The running software in an Environment is referred to as a Stack. The Stack represents a single Deployment of a Build. In other words, the software running in an Environment relates one-to-one with a specific Build.

A Build is the combination of Build Variable/Secret configuration and source code artifact.

Previews

In response to a repository event, such as a pull request, a Pipeline is able to create a temporary preview Environment. The preview Environment utilizes an existing Environment as the foundation to create the one-off environment.

The preview Environment will remain online until the configured shutdown period elapses.