Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate logpush_job to use output_options #2173

Closed
ShreedhanWise opened this issue Jan 20, 2023 · 2 comments · Fixed by #3171
Closed

Migrate logpush_job to use output_options #2173

ShreedhanWise opened this issue Jan 20, 2023 · 2 comments · Fixed by #3171
Labels
kind/enhancement Categorizes issue or PR as related to improving an existing feature. service/logs Categorizes issue or PR as related to the Logging services. workflow/pending-public-documentation Indicates an issue or PR requires changes to public documentation confirming suitability for use. workflow/pending-upstream-library Indicates an issue or PR requires changes from an upstream library.
Milestone

Comments

@ShreedhanWise
Copy link

Current Terraform and Cloudflare provider version

1.0.0

Description

Cloudflare are replacing logpull_options with output_options which provides new functionality: https://developers.cloudflare.com/logs/reference/log-output-options/

Please can we support the new output_options format?

Use cases

As a user, I would like to export log files as CSV files (which output_options allows) so that I can import them into my datawarehouse natively.

Potential Terraform configuration

  enabled             = true
  zone_id             = id
  destination_conf    = local.destination_conf
  dataset             = "http_requests"
  frequency           = "low"
  ownership_challenge = data.aws_s3_object.challenge_file_seo.body
  output_options = jsonencode({
    where = {
      field_names      = ["BotScore", "BotScoreSrc", "BotTags", "ClientRequestHost", "ClientRequestMethod", "ClientRequestURI", "ClientRequestPath", "ClientRequestUserAgent", "EdgeEndTimestamp", "EdgeResponseBytes", "EdgeResponseStatus", "EdgeStartTimestamp", "RayID", "ClientDeviceType", "ClientIPClass", "EdgeResponseContentType"]
      timestamp_format = "rfc3339"
      output_type      = "csv"
    }
  })
  filter = jsonencode({
    where = {
      key      = "ClientIPClass"
      operator = "eq"
      value    = "searchEngine"
    }
  })
}

References

No response

@ShreedhanWise ShreedhanWise added kind/enhancement Categorizes issue or PR as related to improving an existing feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 20, 2023
@jacobbednarz jacobbednarz added workflow/pending-upstream-library Indicates an issue or PR requires changes from an upstream library. workflow/pending-public-documentation Indicates an issue or PR requires changes to public documentation confirming suitability for use. service/logs Categorizes issue or PR as related to the Logging services. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 22, 2023
@STSweeneyCF
Copy link

This has been flagged with the Data (Logs) team for escalation. PM is currently OOO. Will get an approx ETA from her upon return

Copy link
Contributor

This functionality has been released in v4.27.0 of the Terraform Cloudflare Provider.

Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/enhancement Categorizes issue or PR as related to improving an existing feature. service/logs Categorizes issue or PR as related to the Logging services. workflow/pending-public-documentation Indicates an issue or PR requires changes to public documentation confirming suitability for use. workflow/pending-upstream-library Indicates an issue or PR requires changes from an upstream library.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants