v0.19.0

ENHANCEMENTS:

• add support for 'msteams' recipients (#386)

HOUSEKEEPING:

• build(ci): bump hashicorp/setup-terraform from 2 to 3 (#385)
• maint: prune dead code and tidy up (#387)

v0.18.2

HOUSEKEEPING:

• build(deps): Bump google.golang.org/grpc from 1.57.0 to 1.57.1 (#382)
• build(deps): Bump github.com/hashicorp/terraform-plugin-framework from v1.4.1 to v1.4.2 (#381)

v0.18.1

BUGFIXES:

• client: ensure Summary is set on SDK v2 Diagnostics (#378)

HOUSEKEEPING:

• build(deps): Bump golang.org/x/net from 0.13.0 to 0.17.0 (#377)

v0.18.0

ENHANCEMENTS:

• docs: add environment-wide __all__ note where supported (#371)
• client: improve error handling and reporting (#372)
• docs: add clarity around trigger frequency (#373)

BUGFIXES:

• docs: Fix minor typo in "honeycombio_query_specification" documentation (#369)

HOUSEKEEPING:

• build(deps): Bump github.com/hashicorp/terraform-plugin-framework from 1.4.0 to 1.4.1. (#370)

v0.17.0

ENHANCEMENTS:

• resources/honeycombio_board: deprecate list-style Boards (#365)

BUGFIXES:

• datasource/honeycombio_auth_metadata: doc fix (#361)
• fix Marker client test flake (#363)
• queryspec Orders equivalency (#366)

HOUSEKEEPING:

• build(deps): Bump goreleaser/goreleaser-action from 4.4.0 to 4.6.0 (#352)
• build: bump Golang to 1.20 (#359)
• build(deps): upgrade all libraries to protocol version 5.4 and 6.4 (#360)
• build(deps): Bump crazy-max/ghaction-import-gpg from 5 to 6 (#362)
• build(deps): Bump goreleaser/goreleaser-action from 4.6.0 to 5.0.0 (#364)

v0.16.0

NOTES: this release includes a complete rewrite of the honeycombio_burn_alert resource: migrating it from the Terraform Plugin SDKv2 to the new Plugin Framework.
This was done to fix a number of long-standing bugs related to the recipient block similar to the work done in 0.15.0 for the honeycombio_trigger resource.

As with the honeycombio_trigger resource migration, this work has resulted in some subtle, but non-breaking side effects:

• after updating, the next "plan" will show all burn alert recipients being updated in-place
  • at the core of most all of these bugs was that fact that all of id, type, and target for a recipient were being stored in state. Now only id or the type+target pair will be stored in the state and the plan output should reflect this.
• enforcement of only specifying one of id or type+target is now possible due to the new flexibility gained by migrating to the Plugin Framework. Due to the shape of the recipient blocks in the schema, this validation was not possible with the Plugin SDK.
  • in configurations specifying both id and type+target in recipient blocks, the suggestion is to just use id going forward.

FEATURES:

• New Datasource: honeycombio_slo (#345)
• New Datasource: honeycombio_slos (#345)
• New Datasource: honeycombio_auth_metadata (#353)

ENHANCEMENTS:

• resource/honeycombio_trigger: add threshold exceeded_limit support (#351)

BUGFIXES:

• client - fix flakey recipient time comparison test (#342)
• resources/honeycombio_burn_alert: recipient fixes (#346)

HOUSEKEEPING:

• build(ci): Bump goreleaser/goreleaser-action from 4.3.0 to 4.4.0 (#341)
• build(deps): Bump github.com/hashicorp/terraform-plugin-framework from 1.3.4 to 1.3.5 (#344)
• build(deps): Bump github.com/hashicorp/terraform-plugin-sdk/v2 from 2.27.0 to 2.28.0 (#347)
• build(deps): Bump github.com/hashicorp/terraform-plugin-framework-validators from 0.11.0 to 0.12.0 (#348)
• build(deps): Bump github.com/hashicorp/terraform-plugin-testing from 1.4.0 to 1.5.1 (#349)
• build(ci): Bump actions/checkout from 3 to 4 (#350)

v0.15.2

BUGFIXES:

• resources/honeycombio_trigger: fix floating point precision comparison bug (#337)
• resources/honeycombio_trigger: resolve trigger recipient panics (#339)

HOUSEKEEPING:

• build(deps): Bump github.com/hashicorp/terraform-plugin-framework from 1.2.0 to 1.3.0 (#318)
• build(deps): Bump goreleaser/goreleaser-action from 4.2.0 to 4.3.0 (#319)
• build(deps): Bump github.com/hashicorp/terraform-plugin-testing from 1.2.0 to 1.3.0 (#320)
• build(deps): Bump github.com/hashicorp/terraform-plugin-framework from 1.3.0 to 1.3.1 (#321)
• build(deps): Bump github.com/hashicorp/terraform-plugin-go from 0.15.0 to 0.16.0 (#323)
• client: update column test to not rename column (#324)
• build(deps): Bump github.com/hashicorp/terraform-plugin-sdk/v2 from 2.26.1 to 2.27.0 (#328)
• build(deps): Bump github.com/hashicorp/terraform-plugin-go from 0.16.0 to 0.17.0 (#326)
• build(deps): Bump github.com/hashicorp/terraform-plugin-mux from 0.10.0 to 0.11.0 (#327)
• build(deps): Bump github.com/hashicorp/terraform-plugin-framework from 1.3.1 to 1.3.2 (#325)
• build(deps): Bump github.com/hashicorp/terraform-plugin-mux from 0.11.0 to 0.11.1 (#329)
• build(deps): Bump github.com/hashicorp/terraform-plugin-framework from 1.3.2 to 1.3.3 (#334)
• build(deps): Bump github.com/hashicorp/terraform-plugin-testing from 1.3.0 to 1.4.0 (#336)
• build(deps): Bump github.com/hashicorp/terraform-plugin-framework-validators from 0.10.0 to 0.11.0 (#338)

v0.15.1

BUGFIXES:

• build(goreleaser): fix regression and set version on released artifact (#316)

v0.15.0

NOTES: this release includes a complete rewrite of the honeycombio_trigger resource: migrating it from the Terraform Plugin SDKv2 to the new Plugin Framework. This was done to fix a number of long-standing bugs related to the recipient block.

This migration has resulted in some subtle, but non-breaking side effects:

• after updating, the next "plan" will show all trigger recipients being updated in-place
  • at the core of most all of these bugs was that fact that all of id, type, and target for a recipient were being stored in state. Now only id or the type+target pair will be stored in the state and the plan output should reflect this.
• enforcement of only specifying one of id or type+target is now possible due to the new flexibility gained by migrating to the Plugin Framework. Due to the shape of the recipient blocks in the schema, this validation was not possible with the Plugin SDK.
  • in configurations specifying both id and type+target in recipient blocks, the suggestion is to just use id going forward.
• the migration has introduced a new bug (#309) affecting only PagerDuty recipients where the default notification severity of critical was being relied upon without specifying a notification_details block.
  • we felt that the benefit of these fixes outweighted the impact of this newly introduced bug
  • the bug has a very straight forward work around (just specify the severity!), documented in the issue (#309)

FEATURES:

• New Datasource: honeycombio_column (#297)
• New Datasource: honeycombio_columns (#297)

ENHANCEMENTS:

• resource/honeycombio_trigger: add evaluation_schedule support (#314)

BUGFIXES:

• client - escape query string when listing burn alerts for an SLO (#301)
• resource/honeycombio_trigger: recipient fixes (#306, #311)

HOUSEKEEPING:

• build(ci): appease the linter gods (#296)
• build(deps): bump codecov/codecov-action from 3.1.2 to 3.1.4 (#298, #307)
• build(deps): bump github.com/stretchr/testify from 1.8.2 to 1.8.4 (#308, #312)
• build(deps): introduce TF Plugin Framework (#305)

v0.14.0

ENHANCEMENTS:

• resource/honeycombio_board: add overlaid charts graph_settings support (#291)
• resource/honeycombio_dataset: add resource import support (#294)

BUGFIXES:

• client: fix marker client test flake (#293)

HOUSEKEEPING:

• build(deps): Bump actions/setup-go from 3 to 4 (#286)
• build(deps): Bump codecov/codecov-action from 3.1.1 to 3.1.2 (#289)
• build(deps): bump Go to 1.19 (#292)
• build(deps): Bump github.com/hashicorp/terraform-plugin-sdk/v2 from 2.25.0 to 2.26.1 (#288)