Skip to content
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

The terraform-provider-aiven plugin returns error after calling terraform validate #98

Closed
lauraureche opened this issue Sep 10, 2019 · 3 comments

Comments

@lauraureche
Copy link

Hello,

We encountered the following error after calling the terraform validate command. We are using the master branch, we tried also the latest released version(1.0.16), terraform version(0.12.8), go version(1.12.8):

Failed to instantiate provider "aiven" to obtain schema: Unrecognized remote plugin message: [ENVY] unable to load env file(s) on init: open .env: no such file or directory

This usually means that the plugin is either invalid or simply
needs to be recompiled to support the latest protocol.

We are doing the steps from here: https://help.aiven.io/en/articles/2370350-aiven-terraform-integration.

Also, I would like to mention that during debug, I discovered that the git.apache.org is down(hashicorp/terraform#22664) and tried also with you branch: mte-replace-git-apache-org, but the same error still appears when I run only the plugin binary:

/go/src/github.com/aiven/terraform-provider-aiven # ./terraform-provider-aiven
[ENVY] unable to load env file(s) on init: open .env: no such file or directory
This binary is a plugin. These are not meant to be executed directly.
Please execute the program that consumes these plugins, which will
load any plugins automatically

Thank you!

@lauraureche
Copy link
Author

I installed go 1.13 and after that the terraform command worked again, but still will not work with the latest terraform docker image because the apk installs the go 1.12.8 version.

@mteiste
Copy link

mteiste commented Sep 11, 2019

I've not run into this issue before could you try the prebuilt binaries in release 1.0.16? Aiven code does not use the envy library directly but some of the libraries we do utilize seem to.

The branch you tried was an experiment and actually a better way to circumvent the issues caused by git.apache.org being down is to use public goproxy (export GOPROXY=https://proxy.golang.org).

@lauraureche
Copy link
Author

Ok, Thank you!

@mteiste mteiste closed this as completed Sep 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants