Closed PJHRobles closed 1 year ago
Hi PJHRobles
The fix will be deployed shortly during the day. Please re-try in a couple of days and let us know in case you still see the issue.
Thanks.
Looks like it's working now. Closing this issue
hi @krikui , is the fix already been deployed ?
I notice @PJHRobles issue has already solved, not sure if this is related. but I got similar issue with his similar environment setup (provider version 3.15.2)
Hello, Yes the issue is resolved and the fix was deployed.
Thank you.
On Thu, 9 Mar 2023, 12:03 er.musthofa @.***> wrote:
hi @krikui https://github.com/krikui , is the fix already been deployed ?
I notice @PJHRobles https://github.com/PJHRobles issue has already solved, not sure if this is related. but I got similar issue with his similar environment setup (provider version 3.15.2)
— Reply to this email directly, view it on GitHub https://github.com/imperva/terraform-provider-incapsula/issues/298#issuecomment-1461709509, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB567JXZHWZBGFJ2VV3RTWTW3GTG3ANCNFSM6AAAAAAVOFRGLY . You are receiving this because you were mentioned.Message ID: @.***>
Confirmation
Terraform and Imperva provider version
Affected resource(s)
Terraform configuration files
Debug output
-
Panic output
No response
Expected output
Changes are applied
Actual output
Getting a 403 which does not make sense because the API user has the appropriate permissions
Steps to reproduce
plan and apply
Additional factoids
References
No response