[Grafana Dashboards] Missing support for Dashboards V2 schema (aka Dynamic Dashboards)

[hatamiarash7]

Terraform Version

v1.14.5

Terraform Grafana Provider Version

4.25.0

Grafana Version

12.3

Affected Resource(s)

grafana_dashboard (resource)

Terraform Configuration Files

resource "grafana_dashboard" "general_traefik" {
  config_json = file("/etc/grafana/dashboards/general/traefik")
  overwrite = true
}

Expected Behavior

1. With the current version of the provider, we cannot use dashboards in YAML format. This format is currently available within the dashboard and can be exported ( V1 Resource / V2 Resource ).

Error: invalid character 'a' looking for beginning of value

apiVersion: dashboard.grafana.app/v2beta1
kind: Dashboard
metadata:
...
...

2. Even if we use V1 Resource or V2 Resource in JSON format, we will encounter an error when applying.

Error: [POST /dashboards/db][400] postDashboardBadRequest {"message":"Dashboard title cannot be empty","status":"empty-name"}

---

Will support for new models be added to the provider?

[LukaSvastVolue]

@cashia @nlesniak7 fyi

[jan-mrm]

there seems to be a new resource for dashboards grafana_apps_dashboard_dashboard_v1beta1 but currently when exporting a dashboard we already get them in format of version v2beta1 and for that there seems to be no Terraform resource yet 😕

[radiohead]

This has slipped through the cracks on our end, we are looking into it. The fix here would be adding a new resource (similar to grafana_apps_dashboard_dashboard_v1beta1).

[jamesdangercarpenter]

Does this not work for Grafana Cloud?

│ unknown (post dashboards.dashboard.grafana.app)

[jan-mrm]

Does this not work for Grafana Cloud?

│ unknown (post dashboards.dashboard.grafana.app)

Wild guess @jamesdangercarpenter : your trying to use grafana_apps_dashboard_dashboard_v1beta1 but get that error?
yes it should work with Grafana Cloud, but you probably did not set the stack_id in your terraform provider, correct?
At least I ran into that same issue. Was thinking about opening an issue for that, to maybe make the error message more clear or update the docs with the hint or some validation about provider inputs.