We've integrated AWS, GCP and Azure credentials into env0! It's now easy to store AWS, GCP and Azure credentials in env0, give them a name, and explicitly set them for the project of your choice. As well as being much easier to set up, there is more clarity regarding which credentials a project or environment is using for its deployments.

Managing software versions of your Infrastructure as code framework is one of the basic aspects when managing your deployment and code. This becomes more complex when dealing with Terragrunt, as this requires managing both Terraform and Terragrunt versions and making sure they are aligned for each Template you have. Now you can control your Terragrunt version at the template level as well as your Terraform code.

Creating a web experience where navigating easily through a platform is a very hard thing to accomplish.
With the fast and quick changes we do in the platform on a daily basis, it's hard to keep the navigation as simple as possible, especially when releasing new features.
That's why we are introducing a new and easy way to navigate and search through the env0 platform using a Cmd/Ctrl-K shortcut. The search box allows you quick access to different settings and logical entities simply by typing their name or browsing via hierarchical structure 😎

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.