We’re excited to announce Drift Cause, bringing visibility and accountability to managing infrastructure drift.

When detecting a drift, have you ever wondered what caused it, who made the change, and why? Drift Cause helps answer these questions by providing detailed information about who was responsible when it occurred, and how it was triggered—whether through a CLI command, a manual UI update, or another action.

By linking codified infrastructure with out-of-code audit logs, Drift Cause gives teams the context they need to efficiently investigate, resolve, and prevent future drifts.

Drift Cause connects codified infrastructure with real-world changes, offering a clear view of the user responsible for a change, the method used (e.g., UI, CLI, API), and the exact time the change occurred.

You can also drill down into event metadata, such as IP addresses or JSON logs, directly in the cloud provider’s console.

To learn more about how to use Drift Cause, visit here.

Tasks now support custom flows!

With this update, you can now configure custom hooks for your tasks, allowing you to define specific setups and teardowns for all ad-hoc tasks.

For example, if you want to set up specific credentials for all running tasks, you can create an additional step called "Setup Credentials" using custom hooks and configure the credentials as needed.

You can learn more about the available hook options here.

Please note that your custom flows could be set up individually, by creating an env0.yml file with the rest of your configuration, or by using a global policy that will be set on every environment in your project.

Visit here to learn more about setting up project-level custom flows.

Cloud Compass now supports Microsoft Azure, expanding its multi-cloud support.

With this update, Azure users can now:

• Track IaC Coverage: Use AI-assisted logic to analyze your cloud footprint and identify gaps in IaC coverage.
• Assess Risks: Continuously monitor activity across your cloud accounts to identify high-risk assets.
• Streamline Importing: Securely and quickly codify your resources, using GenAI to create custom import blocks.

Read more here

Our latest updates enhance flexibility in hybrid agent configurations and improve sensitive variable management.
Together, these improvements give you greater control over agent setup and secure data handling, simplifying the management of complex environments with increased flexibility and confidence.

Hybrid Agent Support for Flexible Workflows

Projects using self-hosted agents can now operate alongside those using SaaS agents within the same organization, allowing for seamless transitions between different agent types.
This hybrid setup option lets you choose the best agent configuration for each project, improving workflow efficiency and optimizing scalability and resource management. Read more

Secured Variables for Self-Hosted Agents

With this update, sensitive variables securely stored in env0 SaaS are now accessible to both SaaS and self-hosted agents.
Fully encrypted and protected, these variables ensure secure operations across all agent types, enabling seamless transitions while maintaining the highest levels of security. Read more

Simply upgrade your agent to the latest version to take advantage of these new capabilities.

The latest upgrade to our Environment Discovery feature makes onboarding your existing environments to env0 faster and more efficient than ever before.

With this capability, you can add your existing environments in bulk without needing to rebuild them from scratch, reducing manual work and minimizing the risk of errors.

Here is how it works:

1. Activate Environment Discovery and scan your Git repository for existing environments.
2. After the scan is finished you'll get a list of all discovered environments.

Note that for each you also see the name of the project where the environment will be placed (as defined by your Environment Placement configuration).

3. If needed, configure project credentials and Terraform/OpenTofu variables and click ‘Import’.

And that's it.

Once the import process is complete, your environments will be fully managed by env0, subject to all your governance policies, and benefit from platform features like automation, auditability, and more.

Ansible is an open-source automation tool used for configuration management, application deployment, and task automation. It allows users to define their systems and infrastructure as code using simple, human-readable YAML files. We are excited to announce that Ansible now gets first-class support in env0!

✨ Ansible - How does it work ✨

Deploy your playbooks as env0 environments, with all the benefits you know and love, like Approval Flow, Plan on Pull Request, Drift Detection, TTL, Scheduling, and a whole lot more!

In order to manage your Ansible deployments using env0, you will need to create a new Ansible template, or run an environment directly from a VCS and choose the Ansible type:

Read more here.

We're excited to unveil Cloud Compass, a new feature designed to enhance your visibility and understanding of cloud resource management. 🌟 With Cloud Compass, you can analyze and visualize your IaC coverage trends over time, ensuring alignment with your organization’s guidelines. 📊✨

Curious about your resource management types? Our intuitive pie charts provide a clear snapshot of your current distribution, allowing you to understand and strategize better. 🥧📈

Explore a detailed breakdown of your resources and the types of actions performed on them, helping you gain a comprehensive view of your cloud activities. 🔍 Each resource comes with a severity score, allowing you to prioritize tasks for optimal management practices. 🔝

Ready to take control and enhance your cloud management practices? Cloud Compass is here to guide you every step of the way! 🌍💪

Please note that this is a beta feature and we welcome your feedback to make it even better, with each organization currently limited to connecting a single cloud account. 🌟✨

Dive in and start exploring today!

We are thrilled to introduce a new feature that allows you to move environments between projects with ease!

This powerful new capability streamlines your project management, offering more flexibility and control over your env0 resources. Whether you’re reorganizing your projects or simply need to shift resources, this feature ensures a seamless transition.

Get Started

1. Navigate to Environment page of the environment you would like to move
2. Open the menu at the top of the card
3. Click Move Environment

3. Select your target project from the list and click Move

4. That's it! you'll be redirected to the redeploy page so you can deploy the environment on the target project

To learn more about the feature, read our docs

You asked for it, and it's finally here! From now on, env0 gives you more control over deploying your environments directly from the VCS using the new feature: GitOps Apply All

Enabling this feature is very simple, all you need to do is go to environment settings and click Continuous Deployment. You can also enable this feature on the project level, by going to Project Settings, clicking Policies and selecting Continuous Deployment. Your changes will be applied to every new environment created in that project.
See Configuration docs for more details.

Once it is enabled, every PR commit will have a comment listing the affected environments by the latest commit to the PR:

The affected environments can be applied (or planned) by running one of the following PR comments:

• env0 apply --all
• env0 apply --path "<glob path>"

Read more about the different commands in our docs

Finally, upon first deployment, a new env0/Apply commit check will be added (on top of the individual deployment commit checks). The commit check will be in progressand will be in success status once all affected environments have been deployed successfully, or failure status if one of the deployments failed.

Managing your team's dependencies between environments is now easier and more powerful than ever! With the newly available approval flow for workflows, you can now define what environments’ plans you would like to review and have more refined control over your workflows.

✨ Defining your environments to require approval✨

Defining the environments in your workflow to require approval can be done in a couple of ways:

1. By defining the new requiresApproval field in the workflow file in the environments definition.

2. By using the UI now available approval checkbox after selecting your desired environment to have approval for.

   

3. By using OPA approval policies for the project/templates applying them to the environments in the workflow.

Once you've defined your workflow to require approvals and it's been run you will be able to go over the pending deployments and have control over continuing/canceling the downstream environments.