When you review your deployments to production, you can't afford to make mistakes. Even when you're fully focused, it can be very challenging to figure out exactly what changed between deployments.
The primitive logs printed by terraform plan lack useful features (which we have become used to) such as filtering capabilities and difference highlighting.
This problem is easily solved by using env0's new Pretty Plan!

One of the main challenges when managing infrastructure as code is drift.
Drift means that the real-world state of your resources is different than your actual code. This can happen if someone is adding, updating or removing resources manually or with some automation tools outside of your Terraform code. env0 can help you detect those drifts and alert you about them automatically, this is done by setting a scheduled deployment task that ends by examining the terraform plan output.

We’ve added a feature to skip automatic state refresh when destroying an environment.
This feature is used in cases where irrelevant mismatches in the state, are causing terraform plan to fail, thus failing the entire process of destroying environments.

Self-hosted agents allow you to run env0 deployment workloads on your own Kubernetes cluster. Now we are making the integration smoother for AWS and GCP (Azure is next in-line) by allowing you to use advanced authentication methods to authenticate the env0 Self Hosted Agent to your cloud provider. This includes Node and SA Auth on AWS EKS and SA Auth on Google GKE. This means that you can now manage your authorization and authentication with the best practices of your cloud provider.

Custom flows are an essential and important feature in the env0 platform, and today we released a new and powerful enhancement to declare environment variables that are persistent between commands and steps in the env0.yml file, and can be used either by other Terraform/Terragrunt commands or in other custom flow commands.

In a previous release, we added dashboard functionality so users and admins could better understand their env0 platform usage. Since so many users rely on env0 for hands-off IaC automation, we wanted to make it even easier to understand env0 usage at-a-glance. Now organization administrators will receive a weekly usage summary on Monday mornings.

Managing variables with Terraform can be quite difficult. Our platform makes it easier to manage those in large scale with some really useful features like variables scope, sensitive variables, variable description and dropdown list.
We've taken this a few steps further by adding native support for HCL and JSON types, and setting variables as required or read only to help manage and protect you terraform deployments.

Keeping track of new features in all the tools you use can be difficult, and you might miss key features that can make your life a whole lot easier, and make the most of the env0 platform. Now you can know what's new in env0 from inside the application.
We will update you on each new feature that we release and you will be able to get a full overview on how to use it and what are the relevant use cases.

We’ve added a new feature for PR plan deployments that lets you rerun a PR plan. In case your PR plan failed due to a configuration or some manual change, instead of creating a new commit to trigger a new PR plan, now you are able to do it easily from the env0 platform.

Would an Infrastructure as Code Management Platform be usable if it didn’t have its own Terraform Provider?
I don’t think so! The team at env0 has built a Terraform Provider to help you manage your env0 via Configuration as Code, and now added the Environment resource