0.15.1

Summary

This release enables the PagerDuty option in the PagerDutyPage component settings which allows users to set PagerDuty as their main source for syncing service dependencies to Backstage.

This feature was disabled due to a limitation on version 0.3.0 of @pagerduty/backstage-plugin-entity-processor which is now fixed and released on version 0.3.1.

Changes

• refactor: enable PagerDuty option on PagerDutyPage (#132) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.15.0

Summary

This release updates the PagerDutyPage component to add a new configurations tab where users can configure how they want to sync service dependencies between Backstage and PagerDuty.

By default, service dependency syncing is disabled. It's an opt-in feature and admins need to be aware of what it does because you might end up deleting existing service dependencies on Backstage or 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.

On this release we also introduced a fix that was preventing users from showing/hiding columns on the service to entity mapping table (#123).

Changes

• refactor: disabled PagerDuty option due to a design limitation on Backstage (#127) by @t1agob
• fix: turned columnvisibility into a static object (#126) by @t1agob
• feat: service dependency sync (#125) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.14.1

Summary

This release refactors areas where JSON.parse was used in unsafe code which leaves the potential for unexpected exceptions.

It also bumps Backstage package versions and fixes a high severity security issue on a 3rd party dependency.

Changes

• chore(deps): bump fast-loops from 1.1.3 to 1.1.4 (#118) by @dependabot
• chore: remove json parse from unsafe code (#121) by @t1agob

This release was made possible by the following contributors:

@dependabot and @t1agob

0.14.0

Summary

Release 0.14.0 introduces support for multi-account configuration. With this release, admins will be able to specify multiple PagerDuty accounts in the same Backstage instance. Support was added across all the components of the plugin:

• Backend: All API routes exposed take account as an optional parameter so you can create and query information from different PagerDuty Accounts. If admins leverage the Entity Mapping feature, the account is now persisted into the plugin database.
• Scaffolder Actions: When the scaffolder action is used on a template it now lists Escalation Policies from all accounts configured so the user can easily select the one they want. The Scaffolder action
  also outputs the account so it can be replaced in the app-config.yaml annotations.
• Entity Processor: If an entity mapping stored in the plugin database contains the account property, the processor will add an annotation to the entity with its information.

This release solves an existing problem for many large organizations that have several PagerDuty accounts for segregation purposes or that result from company acquisitions.

Changes

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

This release was made possible by the following contributors:

@t1agob

0.13.0

Summary

Release 0.13.0 introduces a PagerDutyPage component which can be added to your Backstage menu and allows users to explore advanced PagerDuty configurations. With this release we are adding support for Entity mapping which allows users to easily map existing PagerDuty services to Backstage entities without requiring updates to each service config file.

Below is an example of how the PagerDutyPage looks like when added to a Backstage instance.

Users will be able to see if the entity definition is up to date with the configuration in file or not and chose to persist the changes by manually creating a PR in the source code.

This release also applies a few security patches related to Backstage dependencies.

Changes

• docs: update readme with mapping capability (#114) by @t1agob
• feat: advanced config page (#113) by @t1agob
• chore(deps): bump ws from 8.14.2 to 8.17.1 (#112) by @dependabot

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob

0.12.2

Summary

This release includes a security patch and a bug fix that was allowing users to create incidents without defining the description of incidents after they created the first one. The state of the description property is now being cleaned up on successful incident creation.

Changes

• chore(deps): bump braces from 3.0.2 to 3.0.3 (#107) by @dependabot
• fix: ensures incident description state is cleaned after an incident is triggered (#108) by @t1agob

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob

0.12.1

Summary

Version 0.12.1 updates all backstage dependencies to the latest version. The PR that originated this version was created based on customer request to update @backstage/core-components to version 0.14 (#102).

We decided to use this opportunity to upgrade all packages (see list of upgraded packages below).

Dependencies:

• @backstage/catalog-model
• @backstage/core-components
• @backstage/core-plugin-api
• @backstage/errors
• @backstage/plugin-catalog-react
• @backstage/plugin-home-react
• @backstage/theme

DevDependencies:

• @backstage/cli
• @backstage/core-app-api
• @backstage/dev-utils
• @backstage/test-utils

Changes

• chore: upgrade backstage/core components to version 0.14 (#105) by @t1agob
• fix: correct client test case description (#100) by @mdb

This release was made possible by the following contributors:

@mdb and @t1agob

0.12.0

Summary

This release introduces a new UI component - PagerDutySmallCard - which allows users to still have visibility on the status of their PagerDuty services in Backstage without using so much screen space. This new UI component removes information on incidents and recent changes, and moves insights and on call information to collapsable panels that can optionally be removed.

This feature was initially contributed by @milenkotomic and slightly modify after feedback from other community members.

Changes

• feat: small sized PagerDutyCard component (#95) by @milenkotomic
• chore(deps): bump tar from 6.2.0 to 6.2.1 (#94) by @dependabot

This release was made possible by the following contributors:

@dependabot, @dependabot[bot], @milenkotomic and @t1agob

0.11.0

Summary

This release introduces a few minor changes and fixes that were part of our roadmap.

Users are now able to hide the on-call section

We introduced a new parameter on the PagerDutyCard entity that allows users to completely hide the on-call information section. This feature was mentioned by a few customers and now it is available through an opt-in mechanism.

<EntitySwitch>
  <EntitySwitch.Case if={isPagerDutyAvailable}>
    <Grid item md={12}>
      <EntityPagerDutyCard disableOnCall />
    </Grid>
  </EntitySwitch.Case>
</EntitySwitch>

Creating an incident is now hidden by default when integration-key is missing

Previously the button to create a new incident was disabled if the integration-key configuration was not defined. We have changed that behaviour to completely remove the button from the card as it was causing confusion according to some customers we interviewed.

Added documentation on how to disable the change events tab

The PagerDutyCard component already had the capability to completely hide the change events tab by using the disableChangeEvents property but this feature was not documented. This information is now part of the official plugin documentation.

<EntitySwitch>
  <EntitySwitch.Case if={isPagerDutyAvailable}>
    <Grid item md={12}>
      <EntityPagerDutyCard disableChangeEvents />
    </Grid>
  </EntitySwitch.Case>
</EntitySwitch>

Changes

• feat: hide on-call information (#89) by @t1agob
• feat: hide trigger incident on missing integration key (#88) by @t1agob
• chore(deps): bump express from 4.18.2 to 4.19.2 (#87) by @dependabot
• chore(deps): bump webpack-dev-middleware from 5.3.3 to 5.3.4 (#84) by @dependabot

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob

0.10.0

Summary

This release introduces a new UI to the PagerDutyCard that is used on each Entity Page. This new UI introduces:

• official PagerDuty logo
• clear visibility on incident status and urgency
• service status
• service standards
• visibility on service metrics (total incidents, high urgency incidents, total number of interruptions)
• escalation policy information on the on-call section

This PR also updates the behaviour of some components from the PagerDutyCard.

• the button to contact the on-call user by email is now removed
• the "create incident" button is now completely hidden in case of read-only mode, instead of just disabling the button.

For Scoped OAuth users 👉 This release requires you to add additional scopes to your App Registration in PagerDuty: analytics.read and standards.read.

Changes

• chore(deps): bump follow-redirects from 1.15.4 to 1.15.6 (#81) by @dependabot
• style: refresh PagerDutyCard UI (#82) by @t1agob

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob