Oliver Ford

Actually, I just saw there was a release a few days ago. Note the comments there: https://github.com/tfutils/tfenv/releases/tag/v2.2.3

@smelchior Done, there weren't actually any conflicts, GitHub's warning was just that it was 'out of date', i.e. there was a commit ('update changelog') on master not on this branch....

Hi! Good to hear from you. Sure, I'll look into it.

Thanks @smelchior, so would I (and I'm still here and willing to work on this too fwiw 🙂). I think I added a passing test as was requested, so good...

I didn't add anything around pushing the resultant image, should be pretty straightforward (especially to GitHub's registry), just needs you to add secret anyway so left it for now. >...

My related PR #303 fixes problems using `-chdir` with `tfenv`'s `terraform` wrapper - but note that *doesn't* close this. My suggestion here was that a `tfenv` configuration could be the...

The docs suggest a bare version, like: ``` required_version = "0.12.5" ``` is parsed as meaning the minimum version required is `0.12.5`. (edit: I tested - `tfenv version-name` errors if...

I don't think it should be an option, all logs should go to stderr. That's one for @Zordrak/bashlog though - it only puts error-level logs to stderr. You can work...

Hm you're right, I can reproduce that. > it looks like info and warn messages go to STDOUT no matter what Yes that's what I meant by only error-level logs...

I would guess it's just been working as expected - @Zordrak is a collaborator with recent commits in tfenv, so I assume so where(/when/if) deemed necessary.