Error if CAA 'iodef' record defined about terraform-provider-namecheap HOT 5 OPEN

I'm not sure why they're not merging it, but #66 has the fix you're looking for.

from terraform-provider-namecheap.

Thanks, and good work! I have a case open with Namecheap and have passed this on. Fingers crossed they actually do something about it.

from terraform-provider-namecheap.

I just tried to add the following records and failed with the error message below.
If I add it in the Web GUI it works without any complaints.

I'm sure somehow the validation logic does not recognise mailto: correctly.

Code

 record {
    address  = "0 issue \"pki.goog\""
    hostname = "@"
    mx_pref  = 10
    ttl      = 1799
    type     = "CAA"
  }
  record {
    address  = "0 iodef \"mailto:[email protected]\""
    hostname = "@"
    mx_pref  = 10
    ttl      = 1799
    type     = "CAA"
  }

Error

│ Error: Records[18].Address "0 iodef "mailto:[email protected]"" must contain a protocol prefix for CAA iodef record
│
│ with namecheap_domain_records.larsartmann_com,
│ on larsartmann.com.tf line 5, in resource "namecheap_domain_records" "larsartmann_com":
│ 5: resource "namecheap_domain_records" "larsartmann_com" {
│

locating the bug

After adding the CAA iodef record manually through the namecheap Web GUI (Image 1), the error stayed the same.
Only after applying CAA issue record manually through the namecheap Web GUI (Image 2), there by fully syncing the real state and the terraform target state, did the error disappear. It's also noticeable that terraform plan did not find anything to do after fully syncing them manually.

from terraform-provider-namecheap.