Support Observability pipeline configuration including the service account

[NasAmin]

Hi,

With the announcement of the new Observability Pipelines, is this something that can be supported via the terraform provider?

Scenario:

For customers with multiple environments, it should be possible to create Observability Pipeline Configuration per environment. This should include generating the Service account with:

• DD_API_Key
• DD_APPLICATION_KEY
• DD_CONFIGURATION_KEY

As required by the Observability Pipelines.

It might also be adequate to use the #1328 datadot_service_account in combination with a new resource datadog_observability_pipeline.

This will truly help with adoption in our case.

Thanks a lot!

References

• Configure Observability Pipeline

[zsherman]

Thanks for filing this issue @NasAmin, I will discuss with the team and post an update shortly!

[NasAmin]

Hey any update on this?

[psemeniuk]

Hi, we're interested in this too. We want to go into Observability Pipelines, but typically each k8s cluster should have dedicated identifiers (like configuration_key) and access tokens. For multiple clusters maintenance burden with an IaC is much lower, than error-prone clicking for each cluster and providing access tokens to some secret manager.

[jamesignatius-cart]

bump on this. Even if it was a data source to fetch the config key, or better yet, the full config instructions as a json, it would make automated integration with a variety of infrastructure really simple