v2.1.1 🌈

🚀 Features

• Chore | Add support for python 3.13 @angelofenoglio (#310)

🐛 Bug Fixes

• Fix | Remove reference to Terraform in error message @angelofenoglio (#312)
• Chore | Update hcl parsing library @angelofenoglio (#309)

📝 Documentation

• Enhancement | Update release-drafter.yml @exequielrafaela (#311)
• Chore: Bump versions of twine and rich @angelofenoglio (#314)

⚙️ Upgrade notes from leverage v1.x to v2.x

• https://github.com/binbashar/le-tf-infra-aws/releases/tag/v2.0.0

📝 Version Compatibility

• Toolbox Docker Image
  • Recommended: 1.6.2-tofu-0.3.0
  • Other working versions:
    • OpenTofu: 1.9.1-tofu-0.3.0
    • Terraform: 1.6.0-0.2.4 1.5.0-0.2.3 1.3.5-0.2.3

🐛 Bug Fixes

v2.0.0 🌈

Changes

🚀 Features / Breaking change

• BL-255 | Add tofu command to cli @angelofenoglio (#305)
  • OpenTofu is now supported under the leverage tofu command, the tf short version that previously was associated to Terraform now will also run tofu underneath. To continue executing the terraform binary the user will have to use the full version leverage terraform. You can find more information in the associated Github Issue: Feature | Starting with tf version 1.7 support and migrate from Terraform to OpenTofu #255
  • OpenTofu Manifesto signature: 🛡 The goals laid out in the OpenTofu manifesto resonate with our core values at binbash. We believe that this initiative is a step in the right direction, safeguarding the principles that have made Terraform a trusted and valuable tool for many.

Upgrade notes from leverage v1.x to v2.x

• https://github.com/binbashar/le-tf-infra-aws/releases/tag/v2.0.0

📝 Version Compatibility

• Toolbox Docker Image
  • Recommended: 1.6.2-tofu-0.3.0
  • Other working versions:
    • OpenTofu: 1.9.1-tofu-0.3.0
    • Terraform: 1.6.0-0.2.4 1.5.0-0.2.3 1.3.5-0.2.3

v1.15.0 🌈

Changes

🚀 Features

• [BL-302] Updating url to prevent sso login url deprecation warning @Franr (#304)
• BL-143 | Version warning @Franr (#299)

🐛 Bug Fixes

• BUG-301 | Fix parsing error in locals.tf and 'config.tf` files @angelofenoglio (#303)
  REMINDER: please remember to add or update the Version Compatibility section before publishing a release draft.

📝 Version Compatibility

• Toolbox Docker Image
  • Recommended: 1.6.6-0.2.3
  • Other working versions: 1.5.0-0.2.3 1.3.5-0.2.3

v1.14.0 🌈

🚀 Features

• The flags for task listing and setting the task definitions file now live within the run command and not the root of leverage.
• Feature | [BV-267] Make sure .gitconfig is always present @Franr (#295)
  • If leverage does not find the needed .gitconfig file it will create it for the user.
• Feature | [BV-599] Kubeconfig helper @Franr (#281)
  • A new discover sub-command has been added to leverage kubectl to simplify management of multiple EKS clusters. discover sub-command documentation.

🐛 Bug Fixes

• Bug | Catch and handle HCL parsing errors @Franr (#296)
  • Leverage no longer crashes showing a long stack trace whenever a config.tf or locals.tf file has malformed syntax. A more friendly message is shown.
• Bug | BL-276 | Copy symlinks for common-variables.tf @Franr (#297)
  • When creating a new project, Leverage now respects symlinks in the template instead of just copying the original file.
• Bug | Catch error for not found/forbidden role @angelofenoglio (#288)
  • If for some reason the AWS config files were created such that Leverage attempts to assume for which the user has no permission. It will now show an error message instead of just crashing.

Enhancements & Changes

• Enhancement | Move tasks load and list to run command @angelofenoglio (#290)
• chore: deprecate python 3.8 @angelofenoglio (#289)
  • Python 3.8 is no longer supported.
• chore: support python 3.12 @angelofenoglio (#293)
  • Python 3.12 is officially supported.

📝 Version Compatibility

• Toolbox Docker Image
  • Recommended: 1.6.6-0.2.3
  • Other working versions: 1.5.0-0.2.3 1.3.5-0.2.3

v1.13.0 🌈

🚀 Features

• Run toolbox with the host's user @Franr (#269)
  • The operations within the container are now run using the host user instead of root. This simplifies permissions handling in Leverage Reference Architecture files.
• Increase account dir search depth @angelofenoglio (#285)
  • Certain usecases require a more deeply nested folder structure in the Reference Architecture implementation. Leverage formerly only looked up to 5 levels deep, it now supports up to 8 levels deep.
• Increase compatibiliy with podman @angelofenoglio (#284)
  • Some users prefer using Podman instead of Docker as a container manager. Container handling was modified to allow the use of Leverage with Podman.

🐛 Bug Fixes

• Fix issue with argument parsing logic for tf apply @borland667 (#274)
  • Leverage has to provide Terraform with some extra parameters to work correctly on the Reference Architecture. The logic that decides which parameters to add was simplified fixing bugs and reducing the probability of new ones.

🔨 Maintenance

• Add python 3.12 to test workflows @angelofenoglio (#280)
  • Now tests are also run on Python version 3.12

📝 Version Compatibility

• Toolbox Docker Image
  • Recommended: 1.6.0-0.2.0
  • Other working versions: 1.5.0-0.2.0 1.3.5-0.2.0

v1.12.4 🌈

Changes

🚀 Features

• Feature | adding python 3.12 in pyproject.toml @exequielrafaela (#278)

📝 Version Compatibility

• Toolbox Docker Image
  • Recommended: 1.6.0
  • Other working versions: 1.5.0 1.3.5

v1.12.3 🌈

Changes

• Pin requests to 2.31 @Franr (#275)

📝 Version Compatibility

• Toolbox Docker Image
  • Recommended: 1.6.0
  • Other working versions: 1.5.0 1.3.5

v1.12.2 🌈

Changes

• [BB-248] Improving test coverage @Franr (#249)
  • Adds testing for credentials module
• [BB-242] _load_configs_for_credentials test @Franr (#245)
  • Improves testing of credentials use even more!
• Fix portability issues with sed and sort in MacOS & Linux @borland667 (#263)

🚀 Features

• [BB-235] project short name validation @Franr (#250)
  • We now make sure project short name is valid before continuing with the credentials files generation
• [SSO Login] Remove now unnecessary restrictions @Franr (#258)
  • The user can now run leverage aws configure sso from anywhere in the project

🐛 Bug Fixes

• [159] Improve apply arguments parsing logic @borland667 (#260)
  • Users can once again use target arguments with the syntax -target <resource> instead of being forced to use an equals sign in Terraform commands
• [229] Fix issue with --version option @borland667 (#256)
  • Now the version will be displayed regardless of the place where the command runs
• [Snyk] Security upgrade jinja2 from 3.0.1 to 3.1.3 @binbashdevops (#241)
• [Snyk] Security upgrade docker from 24.0.5-dind-alpine3.18 to 24.0.7-dind-alpine3.18 @binbashdevops (#246)

📝 Documentation

• Add Version Compatibility section to release notes @diego-ojeda-binbash (#247)
  • Reminder added to Release notes draft template
• [157] Refactor of build processes and dependency management using Poetry @borland667 (#261)
  • We've deprecated Pipenv in favor of Poetry to modernize Leverage packaging and improve developer experience.
  • Pipelines have also been reworked to reflect this change

📝 Version Compatibility

• Toolbox Docker Image
  • Recommended: 1.6.0
  • Other working versions: 1.5.0 1.3.5

v1.12.1 🌈

Changes

🐛 Bug Fixes

• fix: 'AWSCLIContainer' object has no attribute 'common_conf @rynkowsg (#243)
  • an attribute migration broke the _load_configs_for_credentials function

v1.12.0 🌈

Changes

🚀 Features

• [BB-220] Native SSO profiles @Franr (#232)
  • Improve and simplify the way we manage credentials. This also fix a bug where multiple profiles are involved on the same layer.
• [BB-233] Generic command / Rename generic to shell + fix terraform mount/env-var support @Franr (#239) (#234)
  • New command shell where you can mount volumes and inject environment variables
  • Documentation: https://leverage.binbash.co/user-guide/leverage-cli/reference/shell/
• Enhancement | Suggest login command when token expires @angelofenoglio (#230)
  • More verbose error with instructions

📝 Documentation

• Update README adding try-leverage redirection @martingaleano (#224)

🔨 Breaking changes

Given #232 introduced a new way of handling credentials, you will have to run leverage aws configure sso once on your project after you installed the new version.