Make ownership_challenge
argument optional (or documented) for cloudflare_logpush_job
resources
#1010
Labels
kind/enhancement
Categorizes issue or PR as related to improving an existing feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Current Terraform version
0.14.8
Description
Currently the
ownership_challenge
argument is required when creating acloudflare_logpush_job
resource. However, it is not a required field (in the API) when creating a Logpush job with a destination of either Datadog or Splunk.From the docs:
I can see the thinking here, the majority of destinations do require an ownership challenge, though it means when creating a Datadog job a dummy value needs to be provided e.g.
0
.I think either the argument should be made optional and a note added that it's required for the majority of use-cases, or left as is calling out the workaround for Datadog and Splunk. I'm more than happy to raise a PR for either of these.
The Cloudflare API docs for this also seem to be incorrect, again calling out the
destination_challenge
field as required (I've checked and verified it isn't) not matching up with the Datadog integration guide linked above.Use cases
Creating a
cloudflare_logpush_job
with a destination of either Datadog or SplunkPotential Terraform configuration
N/A
References
The text was updated successfully, but these errors were encountered: