datadog is not one of the available choices

[mathieux51]

Terraform Version

t -version
OpenTofu v1.6.2
on darwin_arm64
+ provider registry.opentofu.org/hashicorp/aws v5.46.0
+ provider registry.opentofu.org/sleuth-io/sleuth v0.4.7

Affected Resource(s)

• sleuth_metric_impact_source

Terraform Configuration Files

resource "sleuth_metric_impact_source" "ingress" {
  project_slug     = "my-project"
  environment_slug = "production"
  name             = "my-service"
  provider_type    = "datadog"
  query            = "sum:nginx_ingress.controller.requests{service:my-service}"
  less_is_better   = false
}

Error Output

Error: Errors creating impact source:  [{Field:auth Messages:[Select a valid choice. datadog is not one of the available choices.]}]

Expected Behavior

According to the documentation, resource should be created

Actual Behavior

Fails

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform init
2. terraform apply -auto-approve

[mathieux51]

Not sure who to ping, seems like @JureMalovrh and @zigomir were the last contributors

[recodedecode]

I am having the same issue with newrelic as the provider_type using sleuth-io/sleuth version 0.3.0. I believe it might be an error with the API response and not this package as looking at the Go code it doesn't appear there is any validation against an actual enum. The GraphQL ImpactProvider (see query here) does list both newrelic and datadog as valid options.

[mathieux51]

@recodedecode The README clearly states there is no support for newrelic whereas datadog is in the Terraform provider documentation as an example for sleuth_metric_impact_source.
I didn't go as far as looking at the Go code 😅.
The GraphQL link you shared doesn't for me 😭.

[recodedecode]

Ok, so I missed that fair call out. However, it's in the docs it's in the GraphQL API (hit the play button) as an apparently valid impact provider and having used this provider for other sources I just tried to tie this one in too.

[JureMalovrh]

Hi @mathieux51, thanks for reporting this.

The issue here is that you didn't provide the integration_slug docs. Hence if you have added any description or comment to DD integration you have created, you will need to pass that info as well.

[JureMalovrh]

@mathieux51 were you able to solve the issue?

[recodedecode]

I was able to get this working with your direction @JureMalovrh but it wasn't obvious as I could not initially find where the appropriate integration_slug value was. I did eventually find it by looking at data returned from the GraphQL API over the Sleuth website network requests for our organisation.

With this I was actually able to create a New Relic impact source. So while it says in the docs on this repo that you can't use New Relic with this provider, it was in-fact possible. I believe this is the case because the provider is simply calling the Sleuth API and performing no checks on the enum internally within the provider.

Hope this helps the next person.

[JureMalovrh]

Yeah, we have a ticket open for exposing integration slugs via UI to enable easier copying and usage. I will close the ticket now and bump the priority of the internal ticket.

[zigomir]

Closing since Datadog has landed with #94