Open i89825 opened 1 year ago
Having the same issue. We have thousands of records for a single domain. It wouldn't be logical to break down a single pipeline.
A workaround discussed in the previously closed issue https://github.com/hashicorp/terraform-provider-azurerm/issues/9816 was to increase the read timeout. I have to stress that you would have to amend the tfstate file as discussed in that issue, for the new value to take effect at the planning stage. Obviously, you also have to update it in your project as well.
Is there an existing issue for this?
Community Note
Terraform Version
0.12.31
AzureRM Provider Version
3.9.0
Affected Resource(s)/Data Source(s)
azurerm_privatelink
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
No response
Actual Behaviour
No response
Steps to Reproduce
No response
Important Factoids
No response
References
We tried the below to fix the issue as mentioned in https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/issues/77 1) Used latest Terraform version 2) Upgraded the provider version 3) Enabled trace logs in tf but couldnt get anything relevant which could have caused this issue 4) Enabled parallelism 5) configured time out value to 60 mins
This did not make any change in the outcome.