✍️ Deployment Comments

Effective communication is crucial for any team, and this is especially true when it comes to deployments. It can be difficult to understand the reasoning behind a deployment and how it fits into the bigger picture.

πŸ•Ή Remote Plans

Centralizing Terraform execution is a great way to make sure you have effective IaC governance. While it’s preferred that teams directly use env0 to run IaC, sometimes you just need to run a terraform plan locally.

πŸ” Environment Locking

Many teams have critical infrastructure that needs to be protected from unplanned or accidental changes. Now, with env0 Environment Locking, project or organization administrators are able to lock an environment to prevent users from making changes.

🌡 Workflow Enhancement

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 easily 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.

πŸͺ΅ Log Forwarding to Google Cloud Logging

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 added integration between env0 and Google Cloud Logging. env0 can now forward your infrastructure deployment logs, giving you the ability to monitor, track and analyze logs.

🎚️ Project Level Custom Flow

Project-level Custom Flows enable you to move a custom flow out of the main repository. Now you can configure a single custom flow file for all environments within a project by pointing to a different custom-flow yaml file. Because this custom flow file can be located in a separate repository, it is possible to separate the actual infrastructure code from your deployment policies and scripts that you would like to run on every deployment.

πŸ“Private Module Registry - Folder Based Modules

The env0 Module Registry is a private registry for Terraform modules, allowing you to share and reuse Terraform modules within your organization privately. Now you can manage multiple modules in the same repo by creating folders inside the same repo for each module, which gives you the ability to manage all of your modules in one repo.

βž• Plugins

With env0, you can keep your development organization's best practices for managing and executing Infrastructure as Code. Today we are happy to announce that we developed Plugins to make software development lifecycle tools and processes easier to integrate.

πŸ”Œ Azure DevOps Integration

env0 is all about making IaC management easier. One of the most enabling capabilities we have for achieving this goal is VCS integration. Until recently, we had full support only for GitHub, GitLab, and Bitbucket, along with their on-premise products. And now, env0 is proud to present Azure DevOps integration - create templates, and private modules and enable continuous deployment features for repositories from Azure DevOps.

πŸ”‘ Personal API Keys

In addition to our web app, you can deploy and interact with env0 using any of these three major options - Terraform Provider, Directly invoking the API, and our Remote Backend. All of the mentioned options require an API Key to be passed so we can authenticate, authorize and audit all your actions in env0. The most convenient approach to generating an API Key is to generate a Personal API Key.