minor other issue that has probably nothing to do with this, that in case of CAA records, the generated resources contain a content and a data field, wild the "same" values (different format), and one has to remove one of them in order to make the import start.
Actual outcome
Running terraform plan reports all imported cloudflare-record resources as "will be updated in-place". Example output:
cloudflare_record.terraform_managed_resource_redactedhash will be updated in-place
~ resource "cloudflare_record" "terraform_managed_resource_redactedhash" {
+ allow_overwrite = false
+ content = "redacted.com"
id = "redactedhash"
name = "redacted_record_name"
tags = []
# (10 unchanged attributes hidden)
}
Steps to reproduce
run cf-terraforming generate with cloudflare-record
Confirmation
cf-terraforming version
cf-terraforming v0.21.0-dev+1bedf8c1500f
Expected outcome
After running
cf-terraforming generate
andcf-terraforming import
, thenterraform import
,terraform plan
should report0 to change
resources.Extra information:
versions: Regarding
cf-terrafroming
version, I've tried the latest release and the one from the current (04.11.2024) master.provider registry.terraform.io/cloudflare/cloudflare v4.45.
minor other issue that has probably nothing to do with this, that in case of CAA records, the generated resources contain a
content
and adata
field, wild the "same" values (different format), and one has to remove one of them in order to make the import start.Actual outcome
Running
terraform plan
reports all importedcloudflare-record
resources as "will be updated in-place". Example output:Steps to reproduce
cf-terraforming generate
withcloudflare-record
cf-terraforming import
terraform plan
References
No response