Skip to content

list_stream_definition MarshalJSON error #2957

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

Open
swordfish444 opened this issue Apr 10, 2025 · 1 comment
Open

list_stream_definition MarshalJSON error #2957

swordfish444 opened this issue Apr 10, 2025 · 1 comment

Comments

@swordfish444
Copy link

Datadog Terraform Provider Version

3.59.1

Terraform Version

1.10.2

What resources or data sources are affected?

list_stream_definition

Terraform Configuration Files

list_stream_definition {
  title = "List Stream"
  request {
    response_format = "event_list"
    
    columns {
      field = "timestamp"
      width = "auto"
    }
    
    query {
      data_source = "logs_stream"
    }
  }
}

Relevant debug or panic output

No response

Expected Behavior

To create the list_stream_definition widget on my dashboard

Actual Behavior

│ Error: error updating dashboard: json: error calling MarshalJSON for type *datadogV1.Dashboard: json: error calling MarshalJSON for type datadogV1.Widget: json: error calling MarshalJSON for type datadogV1.WidgetDefinition: json: error calling MarshalJSON for type *datadogV1.GroupWidgetDefinition: json: error calling MarshalJSON for type datadogV1.Widget: json: error calling MarshalJSON for type datadogV1.WidgetDefinition: unexpected end of JSON input

Steps to Reproduce

  1. Create a dashboard resource with a list_stream widget
  2. Include all required fields according to the documentation:
    • response_format = "event_list"
    • columns with field and width
    • query with data_source

Important Factoids

No response

References

No response

@fpighi
Copy link
Member

fpighi commented Apr 18, 2025

Hi @swordfish444 thanks for raising this.
I wasn't able to reproduce it. I suspect it was either a transient issue with the backend or something specific to your setup. If you can still reproduce it, could you please share the entire resource? If you can't share it publicly, you could do that in a support ticket mentioning this issue. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants