Terraform does not respect gitconfig

[okgolove]

I want to config SSH settings for git using gitconfig files and make Terraform using these settings but currently Terraform completely ignores gitconfig.

Terraform Version

Terraform v1.0.0
on linux_amd64

Terraform Configuration Files

module "test" {
  source = "git@github.com:terraform-aws-modules/terraform-aws-vpc.git"
}

Debug Output

https://gist.github.com/okgolove/2392f3245375aae488a21bcffd50cbcb

Crash Output

Expected Behavior

Terraform fails with permission denied error but ssh command settings are used by Terraform and there are verbose logs

Actual Behavior

Terraform fails with permission denied error, no ssh command verbose output, so, settings from gitconfig are ignored

Steps to Reproduce

1. git config --global core.sshCommand "ssh -vvv"
2. terraform init
3. terraform apply
4. There is an error git@github.com: Permission denied (publickey). but no ssh command verbose output

Additional Context

Is you set GIT_SSH_COMMAND variable directly everything works and an verbose output is shown:

GIT_SSH_COMMAND="ssh -vvv" terraform init

References

[mildwonkey]

Hi @okgolove !

This appears to be an issue with the upstream go-getter library. This library (eventually) calls git directly, so most of the time it will honor any .gitconfig settings. However there is an exception (according to this go-getter issue: any ssh setting in configuration gets overridden, while any existing GIT_SSH_COMMAND environment variable is not (more details are in the linked issue).

I'll label this so we can keep track of it. Thanks, and sorry for the unexpected behavior!

[okgolove]

@mildwonkey thanks for the description.
Hope one day hashicorp/go-getter#300 will be merged :)

[mvoitko]

The same problem appears with url config in gitconfig.

[DanHam]

@mildwonkey

Hi Kristin,

Any chance of you nudging the right people to get hashicorp/go-getter#300 merged?

The fix for the upstream library has been sitting unloved for over a year! It's a small change that would make a big difference for a lot of folks bitten by this bug!

It's taken an inordinate amount of time to troubleshoot and find the root cause of this issue!

Merging the fix and updating Terraform to use the newer version of go-getter would be very much appreciated!

[n0rig]

@mildwonkey / @DanHam any update on getting hashicorp/go-getter#300 merged?

[raffraffraff]

I hate to bump issue threads (small audience, sorry guys...) but is there any update on this? Our team are about to moved to github.com and I'm documenting the client setup. This is horrible. We are using .gitconfig in our codebases, but this totally breaks our terraform modules that are sourced using git. This forces us to try to implement overrides via .ssh/config, but that's nasty since they are based on the hostname (which is always github.com).

[DanHam]

@raffraffraff

It took just over 2 years 2 months.... but the upstream fix in hashicorp/go-getter#300 has just been merged! 🎉

All we need to do now is wait:

• For someone to release a new version of go-getter with the needed fix
• For someone here to then update the version of go-getter used by terraform in go.mod
• For a version of Terraform to then be released with the fix

[theherk]

hashicorp/go-getter#300 is finally merged. Praise be to @kmoe.