Grafana Plugin Release Notes

0.1.5

  • Dashboards no longer show formatting-only drift: a dashboard loaded from a pretty-printed JSON file (for example read("dashboard.json")) is stored by Grafana in its own compacted, key-reordered form. Previously every sync reported the dashboard as changed and every apply generated a no-op update — pure whitespace and key-ordering noise, even when nothing about the dashboard had actually changed. The dashboard JSON is now compared by content, so an unchanged dashboard stays quiet, and reformatting your source file (reindenting or reordering keys) on its own no longer triggers an update.

  • Requires formae 0.87.0 or later.

0.1.4

  • Contact point settings as resolvables (settingsMap): GRAFANA::Alerting::ContactPoint gains a settingsMap field whose values accept formae resolvables, so a setting can flow in from another resource (even one managed by a different plugin) in a single apply. This is what lets a PagerDuty integration key wire straight into a Grafana contact point:

    settingsMap = new Mapping {
    ["integrationKey"] = pdIntegration.res.integrationKey
}

    Provide exactly one of settings (the JSON-string form) or settingsMap.

  • Provider-immutable fields marked createOnly: fields the Grafana API will not change in place (for example a contact point's name) are now annotated createOnly, so formae replaces the resource instead of attempting an invalid in-place update.

  • Requires formae 0.86.0 or later.

0.1.3

  • Resource type prefix renamed to GRAFANA::: the namespace prefix is now uppercase to match the formae convention (namespace = "GRAFANA"). All ten resource types are affected (folder, dashboard, alert_rule, contact_point, datasource, message_template, mute_timing, notification_policy, service_account, team). The schema generates these names automatically, so PKL forma files that import the Grafana schema don't need any change. Forma files that reference the resource types by string (e.g. in queries) should switch from Grafana::… to GRAFANA::….

0.1.2

  • Resolvable target URL: The Grafana target URL now accepts resolvable references, so you can wire it directly to another resource's output. For example, connect Grafana to a compose stack endpoint without workarounds:

    config = new grafana.Config {
    url = lgtmStack.res.endpoints.at("lgtm:3000")
}

    The Endpoints/EndpointKey pattern still works but is deprecated and will be removed in a future release.

0.1.1

Fix: DataSource resources with default jsonData values no longer cause drift on every sync. Grafana-populated defaults are now recognised as provider defaults.

Fix: Deleting a NotificationPolicy outside of formae (e.g. via the Grafana UI) is now correctly detected during sync. Previously the resource remained in inventory after an out-of-band delete.

Fix: Dashboards and AlertRules that reference a folder via folderUid can now use a resolvable reference (folder.res.uid), ensuring the folder is created before the resources that depend on it.

0.1.0

Initial release of the Grafana plugin as a standalone package built on the formae Plugin SDK.