0.3.1

Summary

Release 0.3.1 removes a limitation that prevented users from enabling PagerDuty as their main source for syncing service dependencies.

With the help of the Backstage team, we were able to implement a few changes that overcome this limitation and users are now able to set PagerDuty as their main source for service dependencies and get their dependencies sync to Backstage for all mapped entities.

Changes

• feat: enable pagerduty service dependency sync (#13) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.3.0

Summary

This release introduces support for service dependency syncing and automatically creating Backstage integrations in PagerDuty for all new mappings.

With these changes, we are reducing the manual effort on configuring integration keys and service dependencies into Backstage configuration files and ensuring they stay in-sync with PagerDuty.

‼️ 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

• refactor: removing PagerDuty sync to limitation in Backstage (#10) by @t1agob
• chore: updating backstage plugin config (#9) by @t1agob
• feat: service dependency sync (#8) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.2.1

Summary

This release fixes an issue with the missing plugin config schema. Without it the Backstage instance will not load.

Changes

• fix: add missing config schema (#6) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.2.0

Summary

This PR adds multi-account support on entity processor. Now if the account property exists in the database for the mapped entity it will get added as an annotation to the Backstage entity.

Changes

• feat: add support for multi account (#4) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.1.0

Summary

This release introduces entity processor capabilities to PagerDuty plugin for Backstage which will allow users to automatically update the entity configuration files according to the setting defined in the new PagerDuty page.

This features makes it easier to map existing PagerDuty services into Backstage entities.

Changes

• release: 0.1.0 (#1) by @t1agob

This release was made possible by the following contributors:

@t1agob