cloudflare_firewall_rule import issue - zone not set #165
Comments
This was referenced Nov 23, 2018
|
Pending direction in #162. Once that is 👍 , I'll port the changes to this resource. |
jacobbednarz
added a commit
to jacobbednarz/terraform-provider-cloudflare
that referenced
this issue
Dec 4, 2018
During an import of the `cloudflare_firewall_rule` resource, the `zone_id` is defined within the composite ID. This value is then populated and synced within `resourceCloudflareFirewallRuleRead` to match the expected schema resource. However, we don't currently set zone (the zone name) anywhere. This becomes problematic on subsequent terraform operations as the Read attempts to sync the schema with the firewall rule and ends up attempting to recreate the resource due to detecting a change. This is a similar issue to cloudflare#161 and is addressed in a similar manner. Fixes cloudflare#165
patryk
pushed a commit
that referenced
this issue
Dec 5, 2018
During an import of the `cloudflare_firewall_rule` resource, the `zone_id` is defined within the composite ID. This value is then populated and synced within `resourceCloudflareFirewallRuleRead` to match the expected schema resource. However, we don't currently set zone (the zone name) anywhere. This becomes problematic on subsequent terraform operations as the Read attempts to sync the schema with the firewall rule and ends up attempting to recreate the resource due to detecting a change. This is a similar issue to #161 and is addressed in a similar manner. Fixes #165
boekkooi-lengoo
pushed a commit
to boekkooi-lengoo/terraform-provider-cloudflare
that referenced
this issue
Feb 28, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
terraform import for cloudflare_firewall_rule resource forces a new resource on next apply as zone is not added up on import.
zone: "" => "domain.name" (forces new resource)Similar to #161
provider.cloudflare 1.9
The text was updated successfully, but these errors were encountered: