-
Notifications
You must be signed in to change notification settings - Fork 507
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
Add support for private terraform repos #631
Comments
Looks like terraform cloud auth is done via bearer token, so just need to see if we can add support for that. Think I see how to do so, will tinker over the weekend. |
@jlk you mean |
Is there any progress on this? |
hey @MrMickS yep - a little longer than my "over the weekend" comment, sorry. :) Wasn't quite as easy as I first thought - we can't just replace the http client, so I had to figure out some of terraform's data structures, plus I've got a few other things going on. I've got something working POC late last week - adding in ability to read that from |
That sounds great. Thanks very much. |
@MrMickS - Just merged in support for this. if you're eager, you can try with the latest version of the master branch, otherwise we should be cutting a new release in the next week or two. It should Just Work - light mention in the docs at https://github.com/accurics/terrascan/blob/master/docs/usage.md#private-terraform-module-repositories If there's an issue, let's address in a new GH issue (this was auto-closed when I merged the PR). Hope it meets your needs! |
The downloading from TF Cloud works well. Thanks. |
Description
A terrascan user posted on Accurics Community that when using terraform modules stored on Terraform Cloud, terrascan fails at downloading the private module.
While terraform will make use of the token stored in
~/.terraformrc
as documented here, terrascan doesn't seem to know of this...yet.What I Did
I cloned the aws tf module over to a private tf.io repo for testing, along with a basic
main.tf
that references it. Scanning that project dies as seen below:The text was updated successfully, but these errors were encountered: