Closed Zack-Watt closed 2 years ago
@Zack-Watt Please use parallelism=1 and see if the issue is reprodeced
@BrachaY Wasn't positive on what agent we're running. Pretty sure we're running the cloud agent. Attempted both methods in environment variables just to make sure though. All plans produced the same plan of adding our 14 rules, and then same error we've seen when attempting to run the apply.
»Parallelism
You can use the TFE_PARALLELISM environment variable when your infrastructure providers produce errors on concurrent operations or use non-standard rate limiting. The TFE_PARALLELISM variable sets the -parallelism=
Anything else that I should try?
@Zack-Watt Please attach the provider logs in debug mode - add TF_LOG=DEBUG before the terraform apply command
I've attached plan/apply logs.
Hi @Zack-Watt For some reason you added the prefix "integration" to all rule ids. remove it and it will work for you. In addition, we will fix the bug that let you put this id in the first place - the id should be validated according to a close list of ids.
that worked. Looks like we added that for our integration environment as a naming convention and didn't realize that wasn't meant to be changed.
Thank you for the help.
Error: Provider produced inconsistent result after apply When applying changes to incapsula_waf_security_rule, provider "provider[\"registry.terraform.io/imperva/incapsula\"]" produced an unexpected new value: Root resource was present, but now absent. This is a bug in the provider, which should be reported in the provider's own issue tracker.
Updated version to 3.5.1, also failed on version 3.2.2
Example: