[REQUEST] Determine best path forward for Terraform binary management
jake-skipper opened this issue · 0 comments
Is your feature request related to a problem? Please describe.
Currently Runway uses an older / forked version of tfenv for managing Terraform binaries. This has been problematic in the past causing failed downloads, and adds significant upkeep for a function that may be better managed separately from Runway.
Describe the solution you'd like
As we push to simplify Runway into a more maintainable form, we may want to consider removal of this automated binary download process. It's prone to failure at times and it isn't immediately obvious to users which terraform is being used if they have a local install. It also encourages modules with differing levels of terraform versions, which can add even more confusion.
Describe alternatives you've considered
We should consider the impact of having Runway look to the system path for terraform. Users could manage it using their preferred tool (tfenv, asdf, curl, etc). This aligns with our strategy for some other options in Runway, such as Serverless support:
- npm installed on the system
- Serverless must be a dev dependency of the module (e.g. npm install --save-dev serverless)