Skip to content

Releases: grafana/terraform-provider-grafana

v3.1.0

05 Jun 16:01
5ab97ee
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.0.0...v3.1.0

v2.19.1

05 Jun 16:01
fd79c5e
Compare
Choose a tag to compare

What's Changed

  • Contact Points: Avoid 500 errors by listing by @julienduchesne in #1612
  • (V2 Backport) Fix deleting mute timings that are in use (#1608) by @julienduchesne in #1613
  • Update OnCall escalation type param to be required (#1575)
  • Update synthetic monitoring frequency value validation (#1561)

Full Changelog: v2.19.0...v2.19.1

v3.0.0

14 May 18:21
3e2cef5
Compare
Choose a tag to compare

Recommended upgrade procedure

Bump the Terraform provider to the latest v2 version, apply, then upgrade to v3 and remove/replace all the attributes that have been removed.

Major features

Terraform Config Generation (Alpha version)

See the README here.

This is a new tool that will be developed further in future releases. It can be pointed at a Grafana instance or at a Grafana Cloud account and it will find all Grafana provider resources and generate the Terraform config for them.

Example (with the binary from this release):

./terraform-provider-grafana-generate_3.0.0_darwin_arm64 --output-dir test --grafana-auth=admin:admin --grafana-url=http://localhost:3000/

Grafana 11 Support

Some Terraform features had to be removed to enable full Grafana 11 support. All resources should now work with Grafana 11 (Cloud, on-prem Enterprise and on-prem OSS).

Breaking changes

Removed the global (provider-level) org_id setting

Reasons for its removal:

  • The attribute was already added on each resource, so it doesn't remove any functionality
  • It's irrelevant to all parts of the provider other than Grafana resources, possibly causing confusing since there's also an org concept on cloud resources
  • Even for Grafana, it does not apply to all resources. For example, users are not org-scoped. By setting it on a resource level, this is much better defined
  • When using it globally, it prevents looping on multiple orgs. Ex: Create dashboards for a list of orgs. Providers cannot be created dynamically

Removed support for old ID separators (converge on :)

This makes importing resources consistent across all parts of the provider. For example:

terraform import grafana_folder.test orgID:folderUID
terraform import grafana_dashboard.test orgID:dashboardUID

Removed deprecated resources

  • grafana_api_key: Use grafana_service_account instead
  • grafana_cloud_stack_api_key: Use grafana_cloud_stack_service_account instead
  • grafana_cloud_api_key: Use grafana_cloud_access_policy instead
  • grafana_oncall_action : Use grafana_oncall_outgoing_webhook instead

Removed deprecated attributes

  • Removed numerical IDs (of dashboards, folders, datasources) in favour of UIDs
  • grafana_report dashboard definition converged onto a single dashboards {} block
  • cloud_api_key provider attribute: Use cloud_access_policy_token instead

Changelog

New Contributors

Full Changelog: v2.19.0...v3.0.0

v2.19.0

10 May 13:45
3415189
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2.18.0...v2.19.0

v2.18.0

19 Apr 15:53
bd9bdad
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.17.0...v2.18.0

v2.17.0

12 Apr 17:56
631b1bd
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2.16.0...v2.17.0

v2.16.0

10 Apr 20:07
e58c3df
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.15.0...v2.16.0

v2.15.0

05 Apr 15:58
a7fbb01
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2.14.3...v2.15.0

v2.14.3

22 Mar 16:33
603ca62
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.14.2...v2.14.3

v2.14.2

19 Mar 15:03
f567d37
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.14.1...v2.14.2