Skip to content

Feature: support "all fields" option for logpush output_options.field_names #6967

@Zapfmeister

Description

@Zapfmeister

Is your feature request related to a problem?

When configuring cloudflare_logpush_job with output_options, every field must be listed explicitly in field_names. There is no wildcard or "all fields" option. This leads to:

  • Manually maintaining long field lists per dataset (gateway_dns has 78+ fields, gateway_http 55+ fields)
  • Missing fields when Cloudflare adds new ones to a dataset
  • Error-prone configuration — misspelled or missing field names silently result in incomplete data
  • Omitting field_names entirely sends only defaults (essentially just Datetime), which is not useful

Describe the solution you'd like

Support a way to request all available fields for a dataset. Options:

Option A: Special wildcard value

output_options = {
  field_names = ["*"]
}

Option B: Explicit boolean flag

output_options = {
  all_fields = true
}

Option C: Provider automatically fetches available fields from GET /accounts/{account_id}/logpush/datasets/{dataset}/fields when field_names is not specified, instead of falling back to defaults.

Describe alternatives you've considered

Currently we maintain explicit lists of all fields per dataset, fetched from the Cloudflare docs. This works but requires manual updates when new fields are added.

Additional context

This would also be valuable as a Cloudflare API feature — the logpush API itself could support a wildcard in the output_options.field_names array. The Terraform provider could then pass it through, or implement Option C as a provider-level convenience.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementCategorizes issue or PR as related to improving an existing feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions