-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
git clone over SSH fails for modules hosted in Azure Repos #18869
Comments
Any idea when this will be addressed? We’d like to use Azure Devops with Terraform but this has been a major blocker. Would be open to any known workarounds as well if there are any. Our organization is heavy into Azure. |
We are also struggling with this |
I believe this code just wraps go-getter which is just executing |
I was able to get this to work with a URL format like: module "sql_server" {
source = "git::ssh://git@ssh.dev.azure.com/v3/rlacher/Test/Test"
} (note the Let me know if that works for you @tbondal @rlacherksu |
I just tested and it works for me as well- unfortunately I did not think about trying this... (changing : to /) Thanks! //tbondal |
Worked for me as well! Thank you very much. |
Is there an example of this usage in azure-pipelines.yml |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Terraform Version
Terraform Configuration Files
Debug Output
Gist
Crash Output
Expected Behavior
Clone remote Azure Repos repository.
Actual Behavior
Clone failed.
Steps to Reproduce
terraform init
Additional Context
Terraform is running in the Azure Cloud Shell in this example. Also tested with local Ubuntu 16.04 installation on the same Terraform version.
I'm able to successfully clone the repo using the same URL with
git clone
on both systems.References
The text was updated successfully, but these errors were encountered: