-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
authenticating for a module with a private github.com repo source #281
Comments
Hi Kevin, I don't think Atlantis can use those secrets in this case because I don't know how to pass them to Terraform.
|
I just ran into this, another possible way is to configure the git credentials.helper inside the environment / container
|
Got it, thanks for the help everybody. Decided to add a SSH key for the atlantis github user. |
I hit this today. Luckily we pass the git credentials to Atlantis using environment variables, so I enabled |
Related issue: #176 |
Possible implementation of passing the SSH key for a GitHub service account: https://gist.github.com/sryabkov/39f20f263c5edfa650522c6a2e9484b6 |
How are you supposed to do this with the Fargate Deployment? |
You need to build a custom image where you configure the git client and credentials helper in a way that you're able to access your private repositories. For example, the solution @stephencoe presented above works perfectly fine also on Fargate. My solution too; I am running Atlantis on Fargate. |
Seems like this is built in natively now based on #711 - just FYI. |
As far as I can tell, #711 only supports HTTPS authentication via a GitHub token. |
Hello,
I'm trying to use a module sourced from a private github repo:
but I get the following when Atlantis tries to run a plan:
I thought Atlantis would be able to use the same username and personal access token that it used to read the original github private repo.
Thanks in advance for the help!
The text was updated successfully, but these errors were encountered: