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

Install the provider, not recognized by tf v.0.14.5 #74

Open
voehrsCyber opened this issue Feb 11, 2021 · 3 comments
Open

Install the provider, not recognized by tf v.0.14.5 #74

voehrsCyber opened this issue Feb 11, 2021 · 3 comments

Comments

@voehrsCyber
Copy link

Summary

When I tried to install the provider by using the instructions, I wasn't able to get that up and running. I had to change the folder structure and had to tell terraform where to find the provider:

It has to be at a different place now, e.g.
.terraform.d/plugins/cyberark.com/edu/conjur/0.4.0/linux_amd64
and has to be named as:
terraform-provider-conjur

and requires an entry in the main.tf
terraform {
required_providers {
conjur = {
version = "0.4.0"
source = "cyberark.com/edu/conjur"
}
}
}

@BradleyBoutcher
Copy link
Contributor

BradleyBoutcher commented Mar 17, 2021

Hi @voehrsCyber,

I'm sorry you haven't received a response sooner, and thank you for using Conjur!

You're correct in that a manual entry is required as part of terraform v0.13. However, I'm not certain the path you used has to follow that syntax. For example, you could try installing the terraform-provider-conjur binary to .terraform.d/plugins/cyberark/conjur/0.4.0/linux_amd64.

The main.tf entry would look like this:

terraform {
  required_providers {
    conjur = {
      version = "0.4.0"
      source = "cyberark.com/edu/conjur"
    }
  }
}

You can read more about Terraforms provider installation directories here.

All good things,

Bradley
Conjur Community and Integrations Team

@izgeri
Copy link
Contributor

izgeri commented Apr 21, 2021

@voehrsCyber did @BradleyBoutcher's response address your question? I'm wondering if we can close this, or if there is a docs update required here. I'd be glad for your view of the next steps here.

@infamousjoeg
Copy link
Member

@BradleyBoutcher 's solution does not work. There should be successful testing on any proposed workarounds, if manual install is required, and a document update will absolutely be required.

Has there been any traction on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants