Feature | Starting with tf version 1.7 support and migrate from Terraform to OpenTofu

[diego-ojeda-binbash]

Describe the Feature

• First, do an analysis to fully understand the extent of this change.
• Secondly, sketch out a small migration plan (which should include at least affected components, implementation steps, validation and testing, documentation updates required, and communication).
• Finally, proceed with execution of the migration plan.

[exequielrafaela]

Starting with Terraform version 1.7, HashiCorp has transitioned its licensing to the Business Source License (BSL) v1.1. This change imposes specific restrictions on embedding or wrapping Terraform within other tools, particularly those that might compete with HashiCorp's offerings.

To ensure compliance and maintain the integrity of our operations, we propose the following actions:

1. Migrate to OpenTofu: Transition from Terraform to OpenTofu, an open-source alternative that aligns with our commitment to open-source principles and avoids the constraints of the BSL.

2. Update Documentation: Revise all relevant documentation to reflect the migration to OpenTofu, ensuring clarity and accuracy for all users.

3. Notify Clients: Inform our clients about this transition, providing them with detailed information on the reasons behind the change and how it will benefit their operations.

By implementing these steps, we aim to uphold our dedication to open-source values while continuing to deliver high-quality services to our clients.

• Extra Issue: Support terraform again consider:
  Leverage must not embed or wrap Terraform, but can orchestrate and execute any tool (including kubectl , infracost , etc.) and can be used seamlessly in any CI/CD environment.

Sources

• https://www.hashicorp.com/license-faq
  • https://www.hashicorp.com/license-faq#what-does-embedded-mean
• https://terramate.io/rethinking-iac/what-does-hashicorp-s-bsl-busl-adoption-mean-for-terramate/
• https://terramate.io/docs/cli/getting-started/

[exequielrafaela]

• Add conditional to check leverage cli version with leverage-docker-toolbox w/ opentofu
• Consider 1.13.0 breaking change condition that could help as 1st step.

[exequielrafaela]

@angelofenoglio @diego-ojeda-binbash @Franr

Done

• Ref Arch: Layers:
  • Enhancement | Migrate network account layers to OpenTofu le-tf-infra-aws#841
    enhancement minor opentofu
    #841 by Franr was merged 8 hours ago
  • Enhancement | Migrate data-science account layers to OpenTofu le-tf-infra-aws#840
    enhancement minor opentofu
    #840 by martingaleano was merged 5 minutes ago
  • Enhancement | Migrate shared layers to OpenTofu le-tf-infra-aws#839
    enhancement minor opentofu
    #839 by Franr was merged last week
  • Enhancement | Migrate security account layers to OpenTofu le-tf-infra-aws#838
    enhancement minor opentofu
    #838 by Franr was merged 2 days ago
  • Enhancement | Migrate apps-prd account | layers to OpenTofu le-tf-infra-aws#837
    enhancement major
• Leverage CLI: https://github.com/binbashar/leverage/releases/tag/v2.0.0

Pending

1. Tests & CI/CD: Review all tests and CI/CD references to leverage terraform command (@Franr )

   • https://github.com/binbashar/leverage
   • https://github.com/binbashar/le-tf-infra-aws
     • 🧪 Bug | Stabilize KMS Layer Tests After OpenTofu Migration le-tf-infra-aws#846
   • https://github.com/binbashar/le-devops-workflows
   • https://github.com/binbashar/le-tf-infra-aws-template

2. Update Documentation: Revise all relevant documentation to reflect the migration to OpenTofu, ensuring clarity and accuracy for all users. (@angelofenoglio)

   • https://github.com/binbashar/le-tf-infra-aws
   • https://github.com/binbashar/le-ref-architecture-doc
   • https://github.com/binbashar/leverage
   • https://github.com/binbashar/le-tf-infra-aws-template
   • https://github.com/binbashar/le-devops-workflows

3. Notify Clients: Inform our clients about this transition, providing them with detailed information on the reasons behind the change and how it will benefit their operations.