This release introduces several significant advancements designed to enhance the functionality, security, and integration capabilities of Terrakube.

The terrakube-ui container now utilizes the nginxinc/nginx-unprivileged image, replacing the bitnami/nginx image used in previous versions. 

Terraform module versions are now persistently managed within the database, transitioning from the prior Redis-based ephemeral storage. Upon the initial startup following this update, Terrakube will initiate a comprehensive update of all modules. This process may require several minutes, depending on the volume of existing modules. 

 Enhanced support has been implemented for dynamic credential authentication with Openbao or Vault, streamlining secure access and integration with these systems.

Inside the workspace settings it only requires to use the following variables

When running a job for example using the terraform cloud block it will work like the following:

Jobs can now be automatically triggered by merge request and release events within GitLab repositories when defining the webhook configuration like the following:

A gitlab webhook will be created inside the repository

After every job execution a status will be shown inside gitlab 

Support has been added for triggering jobs through pull request and release events in Bitbucket.

The devcontainer environment now offers enhanced support for both PostgreSQL and MSSQL databases, facilitating more flexible development workflows.

The entire project codebase has been migrated to the io.terrakube package structure. Concurrently, all previously defined Quartz jobs have been successfully migrated to this new package hierarchy, ensuring consistency and maintainability.