Closed thatcoleyouknow closed 1 year ago
We opened a support case with Imperva and found this to be a misleading error from the API. The root cause was that our requests were sourcing from an IP that was not in our IP whitelist, which we were not able to identify without asking support to dig through backend logs. I have no clue why using an older provider version was working for us in the mean time but one of the provider devs can probably answer that. If anyone else runs into this error, I'd suggest working with support to identify the true root cause.
Confirmation
Terraform and Imperva provider version
Affected resource(s)
We are using the incapsula_site resource but the error is from the provider (see below)
Terraform configuration files
Debug output
I trimmed the rest of the debug output out cause it was a mile long. If you would like to see it all, let me know.
Panic output
No response
Expected output
No error from the provider and the imperva_site resource is shown in the plan output as expected.
Actual output
Steps to reproduce
terraform plan
Additional factoids
This issue seems to only affects provider version 3.18.1 and above, including latest, which at the time of writing this is 3.20.0. Using a known working API key or generating a new one does not make a difference. I have validated that the API key works via local Postman tests. Provider version 3.18.0 and below are not affected by this issue. We are pinning to 3.18.0 for now until this is fixed.
References
No response