🐞+ 🧼 Monthly Review 🚀 CI/CD Engine
🔥 Fix Terraform version change in deployment*
The issue being addressed is that when a user changes the version of Terraform to a newer one, the backend prompts them to migrate the state, but the version of Terraform is not updated in the frontend.
The development team has fixed this issue and now when a user changes the version of Terraform, the version is also updated in the frontend, and the user is able to perform actions such as plan, apply and destroy. This ensures that the user is always working with the correct version of Terraform, which can prevent errors and improve the stability of the platform.
*Terraform deployment is the process of creating, updating and deleting resources in an infrastructure, using Terraform HashiCorp Configuration Language (HCL) and Terraform API.
When you run terraform plan command, it compares the current state of infrastructure with the desired state, defined in the Terraform code, and it shows the changes that will be made to the infrastructure.
When you run terraform apply command, it applies the changes, defined in the plan to the infrastructure.
When you run terraform destroy command, it removes all resources, defined in the Terraform code from the infrastructure.
During this process, Terraform keeps track of the current state of the infrastructure in a state file, which is usually stored in a remote backend, such as AWS S3, and it can also be stored in a local file.
In summary, the feature fixed the issue with Terraform version change in deployment, where the version of Terraform is not updated in the frontend, causing difficulties for users to perform actions like plan, apply and destroy.
Version and deploy your cloud architecture with Brainboard.