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

Shelling out with terraform: provider "layer0" not available #611

Open
diemonster opened this issue Apr 24, 2018 · 0 comments
Open

Shelling out with terraform: provider "layer0" not available #611

diemonster opened this issue Apr 24, 2018 · 0 comments

Comments

@diemonster
Copy link
Contributor

diemonster commented Apr 24, 2018

When shelling out to terraform, it appears that the parent shell's is not completely inherited. This results in odd behavior such as the output below, when attempting to run system tests via make test.

NOTE: A hacky solution is to make symlinks in every cases directory to the terraform-provider-layer0 binary, but in the case of getent() which is a function defined in the parent shell, it will not propagate to the shell created when shelling out.

NOTE #2: the issue with getent() is worked around if you do not have a ~/.terraformrc file.

go test -v -short -parallel 5 -timeout 15m
=== RUN   TestDataSources
=== RUN   TestDeadServiceRecreated
=== RUN   TestEnvironmentLink
=== RUN   TestImport
=== RUN   TestServiceScale
=== RUN   TestWindowsService
--- SKIP: TestWindowsService (0.00s)
	windowsService_test.go:17: Skipping TestWindowsService in short mode
2018/04/24 11:45:13 endpoint: https://[REDACTED].us-east-1.elb.amazonaws.com
2018/04/24 11:45:13 token: [REDACTED]

2018/04/24 11:45:14 [ERROR] Error running [terraform init] from cases/datasources:
Initializing provider plugins...
- Checking for available provider plugins on https://releases.hashicorp.com...

Provider "layer0" not available for installation.

A provider named "layer0" could not be found in the official repository.
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

1 participant