Releases: vmware/terraform-provider-wavefront
v5.1.0
v5.0.5
v5.0.4
Version using updated GPG key. (Fixes usage with terraform 1.6.0: hashicorp/terraform#33984)
v5.0.3
v5.0.2
v5.0.1
Fixed ACL bug: if the dashboard was not yet created, setting ACL for it would fail.
v5.0.0
dashboard_json
resources, this version of the provider could lead to an inability to modify those dashboards.
The acl
field was previously ignored for the dashboard_json
resource; because, the dashboard API ignored this field. An explicit call to the dashboard acl endpoint is required to set the ACLs.
To be consistent with how the dashboard
resource handles it, the provider now calls the ACL endpoint while saving each dashboard_json
resource.
v4.2.0
- Use a new version of the go client that allows for omissions of the chart
summarization
field from the dashboard chart objects.- This prevents the following API error, in the event the
summarization
field is not included in the JSON body:Cannot deserialize value of type `sunnylabs.query.SummarizationStrategy` from String \"\": was not one of [MEAN, MEDIAN, MIN, MAX, SUM, COUNT, LAST, FIRST, ANOMALOUS]
- This additionally allowed the removal of a patch that set the summarization field to "MEAN" when it was and empty string. The patch led to confusing diffs in the terraform plan, where
summarization
was being set to "" from "MEAN"; even if the field was not provided by the user.
- This prevents the following API error, in the event the
v4.1.0
v4.0.0
This release uses the new go wavefront management api cli version that supports the current Ingestion Policy API. This new API changes the shape of the Ingestion Policy payloads the api expects and returns, meaning the Terraform resources needed to change, breaking existing configurations.*
*Given the SaaS nature of Wavefront, those old configurations would already be broken; so, this change shouldn't impact anyone. However, we will be bumping the major version because it does technically change the config in a non backwards compatible way.