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
, andtarget
for a recipient were being stored in state. Now onlyid
or thetype
+target
pair will be stored in the state and the plan output should reflect this.
- at the core of most all of these bugs was that fact that all of
- enforcement of only specifying one of
id
ortype
+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
andtype
+target
in recipient blocks, the suggestion is to just useid
going forward.
- in configurations specifying both
- 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 anotification_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:
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: