upgrade provider to terraform v0.12.0 #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I tried and it doesn't work with terraform 0.12.0. :( |
|
@djsly I'm using it daily with TF v0.12.4: I have it installed here in my home dir under ...and this is in my |
|
we got it to work. we have to run 2-3 commands during the compilation to have this worked properly. It would be good if a release package could be provided to avoid users to compile themselves :) |
|
@djsly can you share your commands/scripts. happy to build it and push out a release...just want to understand what you are doing so i can tailor it. |
|
we followed this in the end. https://www.terraform.io/docs/extend/terraform-0.12-compatibility.html looks like we needed to do: for the binary to work |
|
@djsly this is my experience. builds fine w/o any of that: |
|
correct the build was fine, but we couldn't use the provider. terraform was telling us, incompatible provider. Maybe it was a fluke, but we tried two different DEV on OSX and Linux and we both had the same errors when trying to run with terraform 0.12.3 |
|
see above . ensure you have similar env. if still no success, let me know. Sounds like you have an older TF. |
|
We are good now though :) my point was more that maybe a release package would make it easier for users to pick you this 0.12 compatible provider :) maybe we should enable the CI file from the original project ? |
|
I'll ask @lawrencegripper how to do that. I have no control over that CircleCI env so unsure how that will work |
|
Basically you should just be able to turn on TravisCI for this repository (Sign up with github login, select this repo and create a build). It should then pickup the existing Travis build config that is in the repository. The only think you'll need to do to get a release published from master is update the |
|
Here are the docs on how to auto publish to github from Travis build https://docs.travis-ci.com/user/deployment/releases/ Nearly all of this is setup, the only thing you'll need to up date your token in the YAML... make sure you use the |
|
Any problems give me a yell. |
davisford
pushed a commit
that referenced
this pull request
Apr 23, 2021
* Basic Cleanup to reduce the needed noise.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrades the provider to the Terraform 0.12.0 SDK.
Confirmed the following commands still work:
go buildmake buildmake testI have not tried it with Terraform 0.12.0 yet, but the migration guide is here and it looks like all that was required is the SDK + deps to be upgraded in this instance.