<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ## Context GitLab ships with [a series of CI templates that reference a GitLab built container with Hashicorp Terraform included](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform.latest.gitlab-ci.yml). The community is already working on [an opentofu based image](https://gitlab.com/gitlab-org/terraform-images/-/issues/114). Hashicorp switched to BuSL template in August 2023. Our internal legal analysis suggests that - we can continue offering all our features as is on GitLab SaaS and Dedicated - we are not allowed to ship the Terraform CI templates with GitLab Self-Managed ### A note for Terraform users GitLab does not plan to remove support for Terraform. We are deprecating the minimal necessary to comply with the BuSL license, this means the CI/CD templates that were shipped with GitLab. All the other functionality is expected to remain. Sometime in the future, we might need to pick Terraform or OpenTofu as the they expected to diverge. This is not needed yet, and we don't want to force anyone to change their preferred IaC tool. This should be your choice, and we want to support you the best we can. ## Proposals ### Proposal 1 - Continue shipping the Terraform CI templates for SaaS only - Replace them with OpenTofu template for Self-Managed. ### Proposal 2 Completely remove the Terraform CI templates from SaaS and Self-Managed, and replace them with OpenTofu templates. ## Replacing the templates 1. We should create new CI templates 2. We should deprecate the Terraform templates and set them up for removal * Instead of a pure purge, we should extend the Terraform templates with a job that educates the user how to switch 3. Drop all (4) the Terraform templates to avoid infringing Hashicorp license. * Could we do this for Self-Managed only? <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->