BUG FIXES:
- Fixes a bug where on-call schedule handoff days were not being updated in FireHydrant
EHNANCEMENTS:
- Adds a new
effective_at
attribute to thefirehydrant_on_call_schedule
resource to allow for scheduling changes to take effect at a future date
BUG FIXES:
- Fixes a bug where escalation policy resources were not being removed from state if deleted outside of Terraform
ENHANCEMENTS:
- New Resource:
firehydrant_inbound_email
(#165) - Adds the attribute for notification priority override to the
firehydrant_signal_rule
resource (#166)
REVERTED:
- Reverted the client-side rate limiting and burst control (#164)
ENHANCEMENTS:
- Resilient client-side rate limiting and burst control (#162)
BUG FIXES:
firehydrant_teams
andfirehydrant_services
data sources are now aware of all pages of teams (#160)
BUG FIXES:
firehydrant_services
data source pulls all services correctly
BUG FIXES:
firehydrant_escalation_policy
example and documentation updated to correctly reflect the usage requirements.
- New Data Source:
firehydrant_ingest_url
(#152). - Added to Resource:
firehydrant_signal_rule
incident_type_id
can now be specified for rules (#153).
BUG FIXES:
EffectiveAt
is now sent for all on call schedule updates. (#154).
firehydrant_on_call_schedule
scheduling strategy now supportscustom
shift durations (#151).
firehydrant_runbook
now supportsrestricted
field for private incidents runbook (#149)
ENHANCEMENTS:
- Added to Data Source:
firehydrant_slack_channel
. Now you can pass either the channel id or the channel name to the data source.
ENHANCEMENTS:
- New Data Source:
firehydrant_slack_channel
(#147). - Improved "resource not found error" with more details of URL.
firehydrant_team
now supportsslug
attribute (#145).
ENHANCEMENTS:
- Bump Go version to 1.22 (#144)
BUG FIXES:
- Resource
firehydrant_on_call_schedule
now handlesmember_ids
correctly. Fieldmembers
has been deprecated. (#143)
BUG FIXES:
- Fixes a bug where handoff steps in escalation policies were assigning to the incorrect schema and causing a panic.
- Add labels to functionalities
- Add initial Signals resources for beta period
- Fix client versioning
- Use timestamps for data source IDs
- Better document how to have runbooks automatically attach
- Bump golang from 1.16 to 1.18
- resource/service: Added
external_resources
attribute to service (#123)
ENHANCEMENTS:
- resource/service: Added
auto_add_responding_team
attribute to service (#117) - data_source/service: Added
auto_add_responding_team
attribute to service (#117) - data_source/services: Added
auto_add_responding_team
attribute to service (#117) - resource/team: Add the ability to attach memberships to teams (#116)
BUG FIXES:
- documentation: Fixed broken links in runbook resource documentation (#101)
BREAKING CHANGES:
- resource/functionality: Removed deprecated
services
attribute, preferringservice_ids
instead (#94) - resource/runbook: Changed the type of the
steps
config
attribute to a JSON string (#79) - resource/runbook: Removed deprecated
type
attribute (#80) - resource/runbook: Removed deprecated
severities
attribute (#80) - resource/runbook: Changed
steps
attribute to be required (#80)
BUG FIXES:
- resource/environment: Fixed bug that prevented the
description
attribute from being unset (#93) - resource/runbook: Fixed bug that prevented the
description
attribute from being unset (#80) - resource/severity: Fixed bug that prevented the
description
attribute from being unset (#88) - data_source/runbook_action: Fixed bug that prevented the Slack
add_bookmark_to_incident_channel
action from working by makingtype
optional (#92)
FEATURES:
- New Resource:
firehydrant_incident_role
(#87) - New Resource:
firehydrant_priority
(#65) - New Resource:
firehydrant_service_dependency
(#89) - New Resource:
firehydrant_task_list
(#85) - New Data Source:
firehydrant_incident_role
(#87) - New Data Source:
firehydrant_priority
(#65) - New Data Source:
firehydrant_severity
(#88) - New Data Source:
firehydrant_task_list
(#85)
ENHANCEMENTS:
- provider: Improved error messages by adding details from the API response (#75)
- provider: Improved documentation for configuring the provider (#95)
- resource/environment: Added logging (#93)
- resource/functionality: Added logging (#94)
- resource/runbook: Added logging (#74)
- resource/runbook: Added the
owner_id
attribute to runbook (#76) - resource/runbook: Added the
repeats
andrepeat_duration
attribute to runbook step (#78) - resource/runbook: Added the
attachment_rule
attribute to runbook (#82) - resource/runbook: Added default value of
false
to the stepsautomatic
attribute (#83) - resource/runbook: Added the
rule
attribute to runbook steps (#84) - resource/runbook: Added documentation for step configuration for every runbook action (#81)
- resource/service: Added logging (#96)
- resource/severity: Added logging to the resource and validation to the
slug
attribute (#88) - resource/severity: Added support for the
type
attribute (#88) - resource/team: Added logging (#96)
- data_source/environment: Added logging (#93)
- data_source/functionality: Added logging (#94)
- data_source/runbook: Added logging (#74)
- data_source/runbook: Added the
owner_id
attribute to runbook (#76) - data_source/runbook: Added the
attachment_rule
attribute to runbook (#82) - data_source/runbook_action: Added logging (#74)
- data_source/service: Added logging (#96)
- data_source/services: Added logging (#96)
NOTES:
- resource/functionality: The deprecated
services
attribute has been removed. See the "Notes" section in 0.2.0 or the original deprecation PR for more information. - resource/runbook: There are a number of breaking changes for the runbook resource. The
steps
attribute is now required, thesteps
config
attribute is now a JSON string, and thetype
andseverities
attribute have been removed. In order to upgrade to 0.3.0, you will need to destroy your existing runbooks and recreate them after changing your configuration to account for the breaking changes. As an example, the configuration below was valid in 0.2.1To upgrade to 0.3.0, that configuration would have to change to the following:# An example of a valid 0.2.1 configuration resource "firehydrant_runbook" "example-runbook" { name = "example-runbook" type = "incident" steps { name = "Send me an email" action_id = data.firehydrant_runbook_action.firehydrant_email_notification.id config = { email_address = "[email protected]" email_subject = "Incident opened on FireHydrant" default_message = "Message" } } }
# The same configuration as above, updated to be valid for 0.3.0 resource "firehydrant_runbook" "example-runbook" { name = "example-runbook" steps { name = "Send me an email" action_id = data.firehydrant_runbook_action.firehydrant_email_notification.id config = jsonencode({ email_address = "[email protected]" email_subject = "Incident opened on FireHydrant" default_message = "Message" }) } }
ENHANCEMENTS:
- documentation: Refactored documentation to follow best practices, added descriptions for all arguments, and added configuration examples for all resources and data sources (#69)
BREAKING CHANGES:
- resource/team: Removed
services
attribute. Use resource/service to associate teams with a service. See "Notes" for more information (#54)
BUG FIXES:
- provider: Fixed bug where errors weren't being checked or handled for various API requests (#58)
- resource/functionality: Fixed bug that prevented the
description
attribute from being unset (#49) - resource/functionality: Fixed bug that prevented the
services
attribute from being unset (#49) - resource/functionality: Fixed bug that prevented functionalities from being removed from state when they had been deleted outside of Terraform (#58)
- resource/service: Fixed bug that prevented the
description
attribute from being unset (#51) - resource/service: Fixed bug that prevented
labels
from being removed from services (#52) - resource/service: Fixed bug that prevented services from being removed from state when they had been deleted outside of Terraform (#58)
- resource/team: Fixed bug that prevented teams from being removed from state when they had been deleted outside of Terraform (#58)
- data_source/runbook_action: Fixed bug that caused the wrong action to be returned when multiple actions existed for the same slug (#56)
ENHANCEMENTS:
- provider: Added Terraform version to the user agent header (#24)
- resource/functionality: Added deprecation warning to the
services
attribute, preferringservice_ids
instead (#49) - resource/service: Added the
alert_on_add
attribute to services (#24) - resource/service: Added the
owner_id
attribute to services (#23) - resource/service: Added the
team_ids
attribute to services (#54) - resource/service: Added the
links
attribute to services (#30) - data_source/functionality: Added the
service_ids
attribute to functionality (#49) - data_source/service: Added the
alert_on_add
attribute to services (#24) - data_source/service: Added the
owner_id
attribute to services (#23) - data_source/service: Added the
team_ids
attribute to services (#54) - data_source/service: Added the
links
andlabels
attributes to services (#30) - data_source/services: Added the
alert_on_add
attribute to services (#24) - data_source/services: Added the
owner_id
attribute to services (#23) - data_source/services: Added the
team_ids
attribute to services (#54) - data_source/services: Added the
links
andlabels
attributes to services (#30)
NOTES:
- The services attribute has been removed from resource/team. If you need to add a team as an owner or responder to a service, use resource/service and specify
owner_id
orteam_ids
. When upgrading to 0.2.0, you should remove theservices
attribute from any team resources and instead addteam_ids
to each service resource. As an example, the configuration below was valid in 0.1.4.To upgrade to 0.2.0, that configuration would have to change to the following:# An example of a valid 0.1.4 configuration resource "firehydrant_service" "service1" { name = "service1" description = "description1" labels = { language = "ruby", lifecycle = "production" } service_tier = 1 } resource "firehydrant_team" "team1" { name = "team1" services { id = firehydrant_service.service1.id } } resource "firehydrant_team" "team2" { name = "team2" description = "description2" services { id = firehydrant_service.service1.id } }
# The same configuration as above, updated to be valid for 0.2.0 resource "firehydrant_service" "service1" { name = "service1" description = "description1" labels = { language = "ruby", lifecycle = "production" } service_tier = 1 team_ids = [ firehydrant_team.team1.id, firehydrant_team.team2.id ] } resource "firehydrant_team" "team1" { name = "team1" } resource "firehydrant_team" "team2" { name = "team2" description = "description2" }
- The deprecated attribute
services
will be removed from resource/functionality 3 months after the release of v0.2.0. You will have until June 30, 2022 to migrate to the preferred attribute. More information about this deprecation can be found in the description of (#49)
BUG FIXES:
- Only one page of results was returned when using
data "firehydrant_runbook_action"
to lookup runbook steps. This meant some steps were completely inaccessible through the provider. This patch will return all steps.
FEATURES:
- CHANGELOG.md added to track contents of each release
IMPROVEMENTS
- The
examples
directory now is separated by resource and includes more and extended examples ofservice
resources
FEATURES:
- Automated release process using GitHub Actions
- Added
service_tier
to service resource
NO CHANGES
IMPROVEMENTS
- Added autogenerated documentation
INITIAL RELEASE