logpush job filter update required after import

[ArnaudCazin]

Confirmation

• This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
• I have searched the issue tracker and my issue isn't already found.
• I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

Terraform v1.10.1
on linux_amd64

• provider registry.terraform.io/cloudflare/cloudflare v4.47.0

Affected resource(s)

cloudflare_logpush_job

Terraform configuration files

resource "cloudflare_logpush_job" "aws_logpush_api_stg" {
  enabled             = true
  zone_id             = var.cloudflare_zone_id
  name                = "aws-logpush-api-${var.tri_staging}"
  destination_conf    = "s3://aws-cfpushlogs-xxx/${var.tri_staging}/api/{DATE}?region=eu-west-2"
  dataset             = "http_requests"
  frequency           = "low"
  # max_upload_interval_seconds = 120
  filter              = "{\"where\":{\"key\":\"ClientRequestHost\",\"operator\":\"in\",\"value\":[\"api-content-rc.domain.tld\",\"api-rc.domain.tld\",\"api-billing-rc.domain.tld\",\"api-oauth-rc.domain.tld\",\"creator-rc.domain.tld\",\"social-rc.domain.tld\"]}}"
  ownership_challenge = "eyJhbGciOiJxxxxxxx"
  output_options  {
    field_names= [
      "ClientIP",
      "ClientRequestHost",
      "ClientRequestMethod",
      "ClientRequestURI",
      "EdgeEndTimestamp",
      "EdgeResponseBytes",
      "EdgeResponseStatus",
      "EdgeStartTimestamp",
      "RayID",
      "ClientCountry",
      "ClientRequestReferer",
      "ClientRequestUserAgent"
      ]
    timestamp_format  = "unixnano"
    field_delimiter  = ","
    output_type      = "ndjson"
    sample_rate      = "0"
  }
}

Link to debug output

cannot provide debug output due to sensitive data

Panic output

No response

Expected output

No changes

Actual output

cloudflare_logpush_job.aws_logpush_api_stg will be updated in-place

~ resource "cloudflare_logpush_job" "aws_logpush_api_stg" {
~ filter = jsonencode(
~ {
~ where = {
- and = [
- {
- and = [
- {
- key = "ClientRequestHost"
- operator = "in"
- value = [
- "api-content-rc.domain.tld",
- "api-rc.domain.tld",
- "api-billing-rc.domain.tld",
- "api-oauth-rc.domain.tld",
- "creator-rc.domain.tld",
- "social-rc.domain.tld",
- "billing-rc.domain.tld",
]
},
]
},
]
+ key = "ClientRequestHost"
+ operator = "in"
+ value = [
+ "api-content-rc.domain.tld",
+ "api-rc.domain.tld",
+ "api-billing-rc.domain.tld",
+ "api-oauth-rc.domain.tld",
+ "creator-rc.domain.tld",
+ "social-rc.domain.tld",
+ "billing-rc.domain.tld",
]
}
}
)
id = "xxxx"
name = "aws-logpush-api-stg"
# (11 unchanged attributes hidden)

    # (1 unchanged block hidden)
}

Steps to reproduce

• Create a Logpush job using the Cloudflare web console.
• Successfully import the Logpush job using Terraform.
• After importing, when running the terraform plan and terraform apply commands, the filter fields are updated even though no resource changes were made.
• Once the proposed changes are applied, the filter becomes inaccessible, invisible, or uneditable in the Cloudflare web console when viewing or editing the Logpush job. (The UI shows a loading spinner, and the filters are no longer displayed.)

Additional factoids

No response

References

No response

[github-actions]

Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of TF_LOG=DEBUG output to be provided. The only parts that should be redacted are your user credentials in the X-Auth-Key, X-Auth-Email and Authorization HTTP headers. Details such as zone or account identifiers are not considered sensitive but can be redacted if you are very cautious. This log file provides additional context from Terraform, the provider and the Cloudflare API that helps in debugging issues. Without it, maintainers are very limited in what they can do and may hamper diagnosis efforts.

This issue has been marked with triage/needs-information and is unlikely to receive maintainer attention until the log file is provided making this a complete bug report.

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.