-
-
Notifications
You must be signed in to change notification settings - Fork 23
Terraform 0.12 support #11
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
Comments
It appears that Terraform is forcing all plugins to close in v0.12, so it doesn't seem possible to keep the SSH connection open by just running them in go routines the way it is currently done. My current thinking is that I'll try to just fork off a new process that can be sent configuration somehow, and then that new process will stay running as long as the main terraform process is running. When the terraform process terminates, the forked process can then exit as well. I was planning to post in the Terraform mailing list to see if the people at HashiCorp have any better suggestions too, but I haven't had the time to do so yet. |
Much appreciated, that makes a lot of sense. HashiCorp has a new forum for technical discussion: https://discuss.hashicorp.com/c/terraform-core I'd be more than happy to take up this issue and put a write up on the forum soliciting comments, sound good? |
Ah, nice. Sure, feel free to create a new topic. I just created a user over there so you can @-mention me in the topic if you'd like. |
Sorry for the long delay/silence on this one. I summarized the state of this provider and the 0.12 issues in a post on the HashiCorp forum: |
I noticed the note in the readme:
Could you share what parts of the upgrade you believe will be nontrivial? This provider would help us out a lot at @TakeScoop, happy to work on the upgrade and support future maintenance!
The text was updated successfully, but these errors were encountered: