0.6.0

Summary

This release adds support to the new Backstage backend system without forcing users to move to the new backend system if they choose to stay in the legacy backend system for now.

Warning: Existing backend plugin users need to make some changes in code because we had to extract the Scaffolder actions to a separate Backstage module (@pagerduty/backstage-plugin-scaffolder-actions).

For existing users using the legacy backend system

1. Install new package

   yarn add --cwd packages/backend @pagerduty/backstage-plugin-scaffolder-actions
   yarn install

2. Update your existing reference in packages/backend/src/plugins/scaffolder.ts from the backend component to the new one

   import { createPagerDutyServiceAction } from '@pagerduty/backstage-plugin-scaffolder-actions';

3. Pass the environment config and logger to createPagerDutyServiceAction

     const actions = [
        ...builtInActions, 
        createPagerDutyServiceAction({ 
             config: env.config, 
             logger: env.logger 
        })
     ];```

For users using the new backend system

1. Install new package

   yarn add --cwd packages/backend @pagerduty/backstage-plugin-scaffolder-actions
   yarn install

2. (Optional) If this is the first time configuring PagerDuty's plugin you also need the following packages

   yarn add --cwd packages/backend @pagerduty/backstage-plugin-backend @pagerduty/backstage-plugin-common
   yarn install

3. Add the package to your backend in packages/backend/src/index.ts

   // PagerDuty backend plugin
   backend.add(import('@pagerduty/backstage-plugin-backend'));
   
   // PagerDuty Scaffolder Actions Module
   backend.add(import('@pagerduty/backstage-plugin-scaffolder-actions'));

Changes

• build(deps): Bump tar from 6.2.0 to 6.2.1 (#53) by @dependabot
• chore: add support to new backend system (#54) by @t1agob

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob

0.5.2

Summary

This release introduces a couple of security patches related to dependencies.

• express (#49)
• webpack-dev-middleware (#51)

Changes

• build(deps): Bump webpack-dev-middleware from 5.3.3 to 5.3.4 (#51) by @dependabot
• build(deps): Bump express from 4.18.2 to 4.19.2 (#49) by @dependabot

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob

0.5.1

Summary

This release fixes a bug related to missing API scopes that was preventing the new capabilities introduce by the new UI (frontend 0.10.0).

Changes

• fix: adds the required API scopes for the new UI (#46) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.5.0

Summary

This release introduces new backend API endpoints to query service standards and service metrics. These features are used by the frontend component to provide additional information on the services.

Changes

• feat: apis supporting new card UI (#44) by @t1agob
• build(deps): Bump follow-redirects from 1.15.5 to 1.15.6 (#43) by @dependabot

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob

0.4.6

Summary

Release 0.4.6 replaces global fetch with node-fetch library as recommended by Backstage on ADR013.

This standardizes on the HTTP package used by the backend plugin and solves issue #37 that prevents HTTP calls to succeed behind a proxy - used in many organizations. This introduces no changes to existing plugin users except for the ones experiencing the behaviour on #37.

Also fixes a security vulnerability by bumping up version of jose from 4.15.4 to 4.15.5.

Changes

• fix: replace fetch with node-fetch to comply with ADR013 (#38) by @pcgqueiroz
• build(deps): Bump jose from 4.15.4 to 4.15.5 (#40) by @dependabot

This release was made possible by the following contributors:

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

0.4.5

Summary

This release updates the config.d.ts values to mark pagerDuty.apiToken and pagerDuty.oauth as secret values.

These are only used by the backend currently and should not be made visible to the frontend. See https://backstage.io/docs/conf/defining/#visibility for more details.

Changes

• fix: ensure secret configuration values are secret (#36) by @alecjacobs5401

This release was made possible by the following contributors:

@alecjacobs5401 and @t1agob

0.4.4

Summary

This release fixes an issue on the on-call section that was retrieving an unordered list of on-call users instead of an ordered list.

It also fixes a security issue on a backstage dependency (@backstage/backend-common).

Changes

• build(deps): Bump @backstage/backend-common from 0.19.9 to 0.19.10 (#32) by @dependabot
• fix(oncall-api): return all users from lowest escalation level (#33) by @brianphillips

This release was made possible by the following contributors:

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

0.4.3

Summary

This release resolves an issue reported in backstage-plugin (#74) which prevents users from overriding the REST API base url (e.g. for EU based accounts). This feature was possible through the Backstage proxy configuration.

With this, users will be able to add a new configuration to the PagerDuty plugin in app-config.yaml like the example below.

pagerDuty:
  apiBaseUrl: https://api.eu.pagerduty.com     #defaults to https://api.pagerduty.com

Changes

• fix: adding support for API base url override (#30) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.4.2

Summary

This release introduces a security patch to a third-party dependency.

Changes

• build(deps): Bump ip from 2.0.0 to 2.0.1 (#29) by @dependabot

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob

0.4.1

Summary

This release changes the start behaviour for the backend plugin. The former behaviour was to prevent the plugin from starting when credentials were missing. This is not the behaviour for most plugins and therefore this release makes that change to comply with existing behaviour.

Release 0.4.1 allows the plugin to start if credentials are missing, logs an error to simplify troubleshooting and shows an error message in the PagerDuty Card.

Changes

• refactor: change start behaviour on missing credentials (#27) by @t1agob

This release was made possible by the following contributors:

@t1agob @jerroydmoore