cloudflare_zone import issue - zone not set

[abohne]

importing a zone doesn't set zone forcing a new resource next plan/apply.

terraform import cloudflare_zone.myzone ba6556bfef261f3373d1d544af786ccb
Import successful!

on next plan
zone: "" => "domain.name" (forces new resource)

Similar to #161 and #165

provider.cloudflare 1.9

[chasen]

I too am having this issue, is there any known workaround?

[chasen]

Found the answer to my own question:

After you import the zone, you can go into your tfstate file and manually update the zone:

"cloudflare_zone.domainName": {
    "type": "cloudflare_zone",
    "depends_on": [],
    "primary": {
        "id": "<ID>",
        "attributes": {
            "id": "<ID>",
            "meta.%": "2",
            "meta.phishing_detected": "false",
            "meta.wildcard_proxiable": "false",
            "name_servers.#": "2",
            "name_servers.0": "mira.ns.cloudflare.com",
            "name_servers.1": "pete.ns.cloudflare.com",
            "paused": "false",
            "status": "active",
            "type": "full",
            "vanity_name_servers.#": "0",
            "zone": "domainName.com" // <-- Add this line
        },
        "meta": {},
        "tainted": false
    },
    "deposed": [],
    "provider": "provider.cloudflare"
},

[jacobbednarz]

cloudflare_zone doesn't have a provider specific import and instead just relies on ImportStatePassthrough which essentially just passes in the ID and then the code makes some assumptions about what it is.

I'll submit a PR to add an Import method to allow setting this instead of relying on the assumptions.

@chasen I don't recommend munging state files by hand as it can often leads to more issues.

[jacobbednarz]

Actually, there isn't any need for me to do anything here. This has already been addressed via #157 and works on master. 1.9 is indeed broken.

[patryk]

Fixed in 1.10.