All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Adding check to on-call relationship step to prevent potential error.
- We are now querying for what 'abilities' are enabled for the querying API key and disabling unsupported steps accordingly.
- Decoupled several steps from building relationships to prevent unnecessary disabling of steps due to a missing 'ability'.
- Fixed broken pagination in PagerDuty integration. Pagination expected a
boolean response body property called
more
, but the property actually exists in the response body atdata.more
.
- Improved messaging for errors from
validateInvocation
.
-
Migrated to latest integration SDK for improved error handling and reporting.
-
Relationships
User - ONCALL -> Service
has been changed toUser - MONITORS -> Service
. Relationships are best expressed as verbs, andMONITORS
is the preferred verb in this type of relationship.
- A number of type check errors after upgrading TypeScript
- New Properties
User
:id
,type
,email
,role
,jobTitle
,timeZone
,billed
,description
,invitationSent
,webLink
- Checking for PagerDuty Admins
- Services active flag always being set to false
- Duplicate relationships between PagerDuty entities
Initial Release