πŸ› οΈ BREAKING CHANGE - Seperate environment "Drift Status" from the Deployment status

Starting Feb 29th, we will enhance user experience by separating Drift Detection and Deployment status into distinct values. This improvement is part of our ongoing efforts to provide users with a seamless and efficient experience. Users will now find it easier to monitor both the latest deployment queue action and any drift detection without the need for extensive deployment log reviews.

πŸ”­ New: Modules Continuous Integration Testing

We're excited to announce our Beta release of continuous integration testing for modules. Built using OpenTofu testing feature, you will now be able to set up testing and integrate it seamlessly into your private module registry. /

⛳️ Partial Workflow Deployment

We are excited to announce that we now support Partial Workflow Deployment.
Partial Workflow Deployment lets you redeploy or destroy a subset of your workflow's graph as needed, rather than running a full top-to-bottom deployment.

🎯 Introducing: Targeted Deployments

Targeting resources and modules allows us to pinpoint exactly what needs to be changed instead of deploying a whole environment. Such selective deployments minimize risks associated with broader changes, ensuring that updates are precise and efficient.

πŸ›œ Remote Apply

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 apply locally.

🀳🏑 Self Hosted Remote State

When orchestrating your infrastructure with Terraform, accessing the state of a remote backend environment securely is a common need. There are instances where safeguarding this sensitive information in house or in a specific region is needed.

πŸ“Š Usage Dashboard

Exciting news! We've just launched the πŸ“Š Usage Dashboard, a handy tool to keep tabs on your system's usage without the headache.

☒️ Breaking Change to Parent and Sub Projects Variables Behaviour

We're happy to announce that starting Dec 10th, variables defined in projects would cascade down to their sub projects.
Environments would not receive only the variables of the project they're defined in, but also the variables of any ancestor project.

πŸ› οΈ BREAKING CHANGE - incoming traffic from env0 extended IP list

The env0 engineering team is dedicated to enhancing the system for increased stability and resilience. As part of our ongoing efforts, we have expanded our resources across more Availability Zones (AZs) and regions, ensuring rapid recovery in the event of a complete AZ or region failure.

πŸ” Easy OIDC Authentication Integration

Usually to authorize yourself in a deployment in env0 you will need to create a deployment credential and assign that credential to the relevant project. That requires keeping long lived credentials in env0.
To avoid that you can use OIDC credentials which are being generated per deployment so you can use short lived credentials. Now you can use OIDC credentials directly by creating an OIDC credential (which requires no sensitive data) and assign that credential to a project and all the setup for the deployment will be done.
You will still need to configure the OIDC provider (AWS, Azure, GCP, Vault etc).
Read more about it here