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

Only a subset of datadog_logs_custom_pipeline imported #1888

Closed
darkn3rd opened this issue Jun 22, 2024 · 3 comments
Closed

Only a subset of datadog_logs_custom_pipeline imported #1888

darkn3rd opened this issue Jun 22, 2024 · 3 comments
Labels

Comments

@darkn3rd
Copy link

darkn3rd commented Jun 22, 2024

When I use terraformer for the datadog provider, only 2 out of 24 logs_custom_pipeline resources are imported.

STEPS

export DATADOG_HOST="https://app.datadoghq.com/apm/home"
export DATADOG_API_KEY="$(awk -F'"' '/datadog_api_key/{ print $2 }' terraform.tfvars)"
export DATADOG_APP_KEY="$(awk -F'"' '/datadog_app_key/{ print $2 }' terraform.tfvars)"
terraformer import datadog --resources='*' 

ACTUAL RESULTS

Only 2 resources imported.

grep ^resource ./generated/datadog/logs_custom_pipeline/logs_custom_pipeline.tf | wc -l
# 2

EXPECTED RESULTS

I expected 24 resources to be imported.

Using the pipelines api, I can get 24 resources using the same key.

curl --silent \
  --request GET https://api.datadoghq.com/api/v1/logs/config/pipelines \
  --header Accept: application/json \
  --header "DD-API-KEY: ${DATADOG_API_KEY}" \
  --header "DD-APPLICATION-KEY: ${DATADOG_APP_KEY}" \
  > output.json
  
jq -r '.[].name' output.json | wc -l
# 24
@darkn3rd
Copy link
Author

Upon further research, pipelines that have is_read_only set to true were not included. It would be nice to have this behavior documented.

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Aug 26, 2024
Copy link

github-actions bot commented Sep 3, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant