Throttling rate limit rules are missing mitigation_timeout field

[jan-verb]

Confirmation

• My issue isn't already found on the issue tracker.
• I have replicated my issue using the latest version of the library and it is still present.

cf-terraforming version

cf-terraforming 0.20.0

Expected outcome

Running cf-terraforming generate --resource-type "cloudflare_ruleset" --zone <zone-id> in a zone with a WAF rate limiting rule that throttles a request generates Terraform with the mitigation_timeout = 0.

Actual outcome

Running cf-terraforming generate --resource-type "cloudflare_ruleset" --zone <zone-id> in a zone with a WAF rate limiting rule that throttles a request generates Terraform without the mitigation_timeout field.

Steps to reproduce

1. Create a WAF rate limiting rule in the UI that throttles a request
2. Run cf-terraforming generate --resource-type "cloudflare_ruleset" --zone <zone-id>

References

Seems related to this issue: cloudflare/terraform-provider-cloudflare#2874

[jan-verb]

The impact of this bug is that throttling rate limiting rules configured successfully in the Cloudflare dashboard fail to terraform apply if generated with cf-terraforming.

Because the rate limiting rule's generated Terraform is missing the mitigation_timeout field, the following error is raised during terraform apply:

Error: Provider produced inconsistent result after apply
When applying changes to module.rate_limit_rules.cloudflare_ruleset.rate_limit_rules, provider "provider[\"registry.terraform.io/cloudflare/cloudflare\"]" produced an unexpected new value: .rules[1].ratelimit[0].mitigation_timeout: was null, but now cty.NumberIntVal(0).

This is a bug in the provider, which should be reported in the provider's own issue tracker.