-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration of terraform from 0.12 to 0.14 documented #141
Comments
This was referenced Dec 23, 2020
Just to say - I hit this issue whilst following Alex's book yesterday. I worked around it as I use https://github.com/tfutils/tfenv to manage multiple terraform versions. |
@Waterdrips could you take over this and move us up to 0.15.0? When done, let me know so I can update existing tutorials and resources. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the DigitalOcean OpenFaaS terraform only works with 0.12.
0.13 and 0.14 are possible without operator expertise, if a specific set of commands is run, in specific situations.
While terraform administrators may know to run these commands; what to run. People coming in from blogs may not be professional administrators and are likely to make noise in Github, twitter, etc.
Expected Behavior
terraform init
either works without error (warnings okay I guess), or gives an error directing to upgrade terraform versions.Current Behavior
terraform init
can give errors in newer terraform versions on greenfield and brownfield deploys.Possible Solution
Link external documentation
Document the migration from 0.12 upwards as a note or aside on articles referencing the affected terraform files.
Currently only digitalocean openfaas one is known about. Terraform actually handles most of this for you, but people need to know where to look and how to approach.
Linking to these drastically cuts down work and improves signposting.
Be more explicit about the current terraform version
Dockerfile, Vagrantfile, or big section "this is / could be old" could very much handle this.
limitations
Both of these approaches only work going forwards. Neither fully meets the desired state of all error messages signposting, which is unfortunate.
Steps to Reproduce (for bugs)
Follow this guide using 0.14, which is the version from the large icons on the terraform download page, no matter your OS.
terraform init
stage 0.14 will not direct to upgrade, like 0.13 wouldContext
To be honest this does not affect me. I know what I'm doing, but I've not always known, and have only been able to know due to good documentation practices and mentoring. It's hard.
Your Environment
N/A (it's the same across OSx, Windows and Linux, I've reproduced on all three.
The text was updated successfully, but these errors were encountered: