🤖 Ad Hoc Tasks

Sometimes you may find yourself wanting to execute arbitrary commands on your deployment container - for example, manually altering the state or manipulating a local file. These commands can be run using Custom Flows, but that requires committing the commands to your git repository, which doesn't always fit the use case. For these cases, it is now possible to execute an ad hoc task on the deployment container.

❗Regex Validation For Variables

env0 Variables is a very powerful tool for maintaining and configuring your infrastructure as code. It can help keep your code DRY, manage secrets and create a hierarchy to manage a large-scale infrastructure. But with great power comes great responsibility, and that's why you can also create policies and checks to validate your variables are intact. Now you can use regular expression validation to prevent users to enter something you didn't mean to prevent errors while deploying your Infrastructure as code.

🎬 Environment Without Template

env0 templates can be very useful, as they enable RBAC and reusability. However, in some cases, you may just want to connect to a repository in your VCS and skip templates for simplicity. To enable this simpler environment creation process, we added a new approach to run directly from your VCS integration without having to create a template.

💯 Feature Complete version for env0 Terraform provider

We are strong believers in Infrastructure as code and strive to codify everything we possibly can, and so do all of our customers. Now with this new release of our Terraform provider, you can do so for your entire IaC deployments, including the env0 platform. This marks a huge effort from the RnD team and the help of the community. Today we are really happy and proud to announce a feature-complete version of our env0 Terraform provider - version 1.0.0

💬 Plan and Apply from PR comments

As software developers, we all use a Version Control System (VCS) as the main tool in our process. With env0 you can also manage your Infrastructure as Code (IaC) deployments directly from your VCS provider.
By commenting with env0 commands on a pull request, it is possible to interact with your env0 environments without the need to login to the env0 platform.

🪵 Log forwarding to Splunk, Datadog and Logz.io

Centralized log systems have been around for a long time, and in today's world they are more than just log aggregators. Metrics, traces, analytics, and other valuable tools are all rolled up into logging systems. Today we've created an integration between env0 and three major platforms — Splunk, Datadog, and Logz.io — to forward all of your infrastructure deployments from env0, giving you the ability to monitor, track and analyze logs with the power of these great tools.

✏️ PR Plan - New Settings

We introduced monitoring infrastructure code changes via pull requests as “Plan on PR” a while ago. Today, we are introducing more ways to control the outcome of this process by enabling new policies. There are now settings for how env0 should act in certain use cases, like TF “skipped” statuses and merge commits.

🍾 Pulumi Support

Pulumi is an infrastructure-as-code framework that harnesses popular programming languages such as Go, JS/TS, Python, and .NET Platform.
Today we are thrilled to announce env0 now supports Pulumi as another IaC framework in addition to Terraform and Terragrunt. Now you can enjoy all of the benefits env0 platform has to offer out of the box with Pulumi like Plan on Pull Request, Drift Detection, TTL, Scheduling and much more...

🔑 Easier Management of Cloud Credentials

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 Terragrunt Version

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.