Skip to main content
Creating a workflow is a great way to have a deployment of your infrastructure and create dependencies between different parts of your infrastructure, allowing you to manage your infrastructure as you scale. However, you may want to have different variables and settings for each part, so today you can do it when creating or deploying a new Workflow. Now we have two new enhancements when working with Workflow environments.

​
Remote Backend In Your Sub Environments

When creating a workflow you are now able to set it to use env zero’s remote backend. That will make all its terraform sub environment use env zero’s remote backend as well. All the rules regarding workspace names for templates and remote backend within env zero organizations still apply.
Workflow configuration interface showing remote backend settings for sub environments

​
PR Plans for Workflow Environments

By creating a Pull Request that targets your workflow environment, you can execute Plan on changes to your branch! It will trigger the Plan for all deployed environments that contain your workflow environment. Any change to the workflow file won’t take effect. env zero will comment and set a commit check for each environment separately so you can keep track of the changes you made!
Pull Request plan execution interface showing workflow environment plan triggers
Pull Request comments and commit checks interface showing separate environment tracking

​
Related Content

Workflow Creation Remote Backend Plan On Pull Request