Open sahinM opened 2 years ago
@sahinM microsoft/azuredevops
is a third part provider supported MS. terraform init
will download the providers form Terraform registry, the URL looks like: https://registry.terraform.io/v1/providers/{org}/{name}/{version}/download/{os}/{arch}
. Does there any WAF or policy that will verify the URls?
Terraform Version
Terraform Configuration Files
main.tf
versions.tf
Debug Output
Expected Behavior
It should be successfully installed with output:
Actual Behavior
Steps to Reproduce
terraform init -backend-config="access_key=${ACCESS_KEY}" ${{ parameters.terraform_backend_config }} -no-color
Additional Context
Our Infrastructure is running in the Azure Cloud using Azure YAML Pipelines within
Azure DevOps
. The providermicrosoft/azuredevops v0.2.1
fails in theterraform init
step in unpredictable cases, therefore until now the TF_DEBUG modes were not used and activated. We would like to have a reliable running CI/CD, but unfortunately this provider makes it unforseenable. Google helped with some directions as in keywords:tls`, `network
issue,
Corrupted data stream along the way,
Firewall / Antivirus is the usual suspect`.Also I noticed that when installing that specific provider
microsoft/azuredevops
it is Signed by a HashiCorp partner with some key ID, just as a site note, that this differs somehow from the other installed providers. So may here is some reason, that something with the installing and signing process is different.Hope that helped a bit for insights.