Leverage

🚀 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](https://hub.docker.com/layers/binbash/leverage-toolbox/1.6.0-latest/images/sha256-0d1f96640fb01e37fb55953b9146d4910f18ea74baf16ceb967829623b68b80f?context=explore)
- Other working versions: [1.5.0](https://hub.docker.com/layers/binbash/leverage-toolbox/1.5.0-latest/images/sha256-e25e42896bbd6beafab2600d80fd2f638f43ba18b866730b27a7a510160a6b42?context=explore) [1.3.5](https://hub.docker.com/layers/binbash/leverage-toolbox/1.3.5-latest/images/sha256-89408970e62dad586a4626c195465fdda88cf1df988d1751e0eb6d3dd62eb321?context=explore)

Changes

🚀 Features

- Feature | adding python `3.12` in pyproject.toml exequielrafaela (278)

📝 Version Compatibility
- Toolbox Docker Image
- Recommended: [1.6.0](https://hub.docker.com/layers/binbash/leverage-toolbox/1.6.0-latest/images/sha256-0d1f96640fb01e37fb55953b9146d4910f18ea74baf16ceb967829623b68b80f?context=explore)
- Other working versions: [1.5.0](https://hub.docker.com/layers/binbash/leverage-toolbox/1.5.0-latest/images/sha256-e25e42896bbd6beafab2600d80fd2f638f43ba18b866730b27a7a510160a6b42?context=explore) [1.3.5](https://hub.docker.com/layers/binbash/leverage-toolbox/1.3.5-latest/images/sha256-89408970e62dad586a4626c195465fdda88cf1df988d1751e0eb6d3dd62eb321?context=explore)

Changes

- Pin requests to 2.31 Franr (275)

📝 Version Compatibility

- Toolbox Docker Image
- Recommended: [1.6.0](https://hub.docker.com/layers/binbash/leverage-toolbox/1.6.0-latest/images/sha256-0d1f96640fb01e37fb55953b9146d4910f18ea74baf16ceb967829623b68b80f?context=explore)
- Other working versions: [1.5.0](https://hub.docker.com/layers/binbash/leverage-toolbox/1.5.0-latest/images/sha256-e25e42896bbd6beafab2600d80fd2f638f43ba18b866730b27a7a510160a6b42?context=explore) [1.3.5](https://hub.docker.com/layers/binbash/leverage-toolbox/1.3.5-latest/images/sha256-89408970e62dad586a4626c195465fdda88cf1df988d1751e0eb6d3dd62eb321?context=explore)

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](https://hub.docker.com/layers/binbash/leverage-toolbox/1.6.0-latest/images/sha256-0d1f96640fb01e37fb55953b9146d4910f18ea74baf16ceb967829623b68b80f?context=explore)
- Other working versions: [1.5.0](https://hub.docker.com/layers/binbash/leverage-toolbox/1.5.0-latest/images/sha256-e25e42896bbd6beafab2600d80fd2f638f43ba18b866730b27a7a510160a6b42?context=explore) [1.3.5](https://hub.docker.com/layers/binbash/leverage-toolbox/1.3.5-latest/images/sha256-89408970e62dad586a4626c195465fdda88cf1df988d1751e0eb6d3dd62eb321?context=explore)

Changes

🐛 Bug Fixes

- fix: 'AWSCLIContainer' object has no attribute 'common\_conf rynkowsg (243)
- an attribute migration broke the `_load_configs_for_credentials` function

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)

:hammer: 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.