0.9.2

Summary

This releases fixes a bug in package.json that was preventing the plugin from being installed in certain installations

Changes

• fix: relax version pinning of @pagerduty/backstage-plugin-common (#100) by @tamimkh
• fix pluginPackages type (#98) by @tamimkh

This release was made possible by the following contributors:

@tamimkh

0.9.1

Summary

This release introduces a few enhancements that to ensure a) no undesired code is executed when an exception is caught, and b) to avoid trying to emit headers multiple times.

Changes

• fix: add missing "return" statements after errors (#83) by @brianphillips

This release was made possible by the following contributors:

@brianphillips and @t1agob

0.9.0

Summary

This release introduces a set of features that were in a way dependent on each other which makes it quite large when compared to a typical release.

• Automated Backstage integration setup for mapped entities: With the goal of simplifying the setup process for mapped entities we introduced a feature that automatically creates a integration on the corresponding PagerDuty service when a pagerduty.com/service-id property is available.

  With this feature, admins can skip the step of creating an integration in PagerDuty and copy the integration key to each Backstage entity file. They can now simply add the pagerduty.com/service-id annotation to their service, or simply use the PagerDutyPage to map existing PagerDuty services to Backstage entities and the plugin will take care of the rest. This change is related to #80.

• Plugin configuration persistence layer: To support two-way sync for service dependencies we decided to give the admins the option of choosing which is their main source of truth and for that reason we introduced a new section in PagerDutyPage where you can specify your preferences. The backend centralises all the persistence layer and this release includes all the necessary methods for it.

• Two-way service dependency sync: This release introduces a way to keep your service dependencies in sync between PagerDuty and Backstage. Admins will be able to choose which source is the main one. This is an opt-in feature that you can enable on the PagerDutyPage under the configuration tab.

  ‼️ Important: Due to a Backstage design decision it is not possible to fully overwrite the relations specified in each entity's configuration file. For that reason the option to synchronise strictly from PagerDuty side is not available.

Changes

• feat: service dependency sync (#81) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.8.2

Summary

This release fixes some potential issues with JSON.parse on unsafe parameters that can lead to unexpected exceptions.

Changes

• chore: refactor JSON.parse usage on unsafe code (#77) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.8.1

Summary

This release bumps all Backstage packages to the latest version to allow an upgrade to 1.29.1 without any warnings on outdated packages.

Changes

• fix: bump deps to work with backstage v1.29.0 (#73) by @jpd4emis

This release was made possible by the following contributors:

@jpd4emis and @t1agob

0.8.0

Summary

This release introduces the necessary changes to support multi-account configurations.

• Plugin database now supports account reference
• All PagerDuty API operations are account aware
• Updated plugin configuration schema to accept multi-account configurations

We made extensive tests to ensure that the existing configuration for a single PagerDuty account still works. Therefore existing customers will be able to upgrade to the latest version without breaking anything.

Changes

• feat: add support for multiple accounts (#71) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.7.2

Summary

This release handles properly an exception that was causing the entity mapping page to break when there is an integration key specified in the entity configuration and that integration key doesn't exist in the PagerDuty Account.

Previously it would return an HTTP 404 error, causing the application to break. Now, it handles that error without breaking the application.

Changes

• fix: ignore invalid integration keys when building entity reference dict (#69) by @brianphillips

This release was made possible by the following contributors:

@brianphillips and @t1agob

0.7.1

Summary

PagerDuty advocates for full-service ownership and one recommendation on that direction is for customers to associate teams with services to state clear ownership of that service. Still, this is not enforced and therefore some customers don't have teams configured.

This release ensures the backend handles empty teams arrays gracefully to prevent the PagerDutyPage component from staying in a loading state indefinitely.

Changes

• fix: handle empty teams array to prevent TypeError (#66) by @MikeSmvl

This release was made possible by the following contributors:

@MikeSamv, @MikeSmvl and @t1agob

0.7.0

Summary

Release 0.7.0 adds support for new entity mapping APIs to be used by the frontend component to allow easy onboarding of existing services from PagerDuty into Backstage. This is a highly requested feature that aims to ease the process of onboarding existing PagerDuty services into Backstage.

This release includes new API endpoints to:

• Get all entity mappings persisted to the database
• Get an entity mapping for a specific Backstage Entity reference
• Persist mappings into the database

These APIs introduce the needed mechanisms to persist data into the database selected by the Backstage Admin. The database table is automatically generated and is exclusively used by PagerDuty plugin Backstage to ensure data segregation.

This release also includes a few security fixes on dependencies used by the Backstage packages.

Changes

• feat: entity mapping persistence (#63) by @t1agob
• build(deps): Bump @azure/identity from 4.0.1 to 4.2.1 (#61) by @dependabot
• build(deps): Bump mysql2 from 3.9.7 to 3.10.0 (#59) by @dependabot
• build(deps): Bump ws from 8.14.2 to 8.17.1 (#62) by @dependabot

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob

0.6.1

Summary

This release adds security patches to fix two moderate and two critical vulnerabilities on mysql2 dependency.

Changes

• build(deps): Bump mysql2 from 3.9.4 to 3.9.7 (#57) by @dependabot
• build(deps): Bump mysql2 from 3.9.2 to 3.9.4 (#56) by @dependabot

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob