-
Notifications
You must be signed in to change notification settings - Fork 372
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
timeboard resource missing support for some field names in "marker" block #50
Comments
I'm also seeing similar when not specifying label values in the Datadog UI which then breaks our CI/CD pipelines for terraform changes.
here is the example marker block as defined in the Datadog API for the graph that breaks terraform builds:
This "label: true" is the syntax for when a string isn't provided in the "label" field in the UI / API. I'm guessing the go http library used by this provider is expecting this to always be a string and sometimes (when no text label is provided) breaks unmarshalling with the expected struct. |
@robinbowes setting marker {
label = "High Latency"
type = "error solid"
value = "0.8 > y > 0"
} |
@tmack8001 correct, the label is expected to be a string here https://github.com/zorkian/go-datadog-api/blob/master/dashboards.go#L44 but this is the case only when the checkmark on the UI is set AND the input type contains some text, otherwise the API returns The correct behaviour IMO would be having another, boolean JSON field in the response representing whether the label checkmark was set or not and always return a string for |
Closing this as the first issue seems invalid and the second one was fixed adding a note to the docs (literally the only thing I can do at this moment). |
I'm attempting to create DataDog timeboards from terraform.
I'm exporting the definitions using the DataDog API and parsing the output to generate terraform config.
It seems that the markers section in the graph definition block supports some field names that are not included in terraform, eg:
Is this just a case of the provider not keeping up with changes in DataDog capabilities?
The text was updated successfully, but these errors were encountered: