Release notes for Scaffolder Actions module

> 0.2.0

Summary

This PR adds support for multi-account configuration to scaffolder actions. It introduces no changes for the end user and adapts to the configuration set in app-config.yaml. If multiple accounts are configured the user will see the list of all Escalation Policies in all accounts with the reference to it's source account.

multi-account escalation policy list

At creation time, the scaffolder will select the correct account to deploy the service to depending on the select escalation policy/account pair selected.

Changes

feat: add support for multi accounts
chore(deps): Bump mysql2 from 3.9.2 to 3.9.7
chore(deps): Bump mysql2 from 3.9.7 to 3.10.0

Dependencies

@pagerduty/backstage-plugin-common: ^0.2.0

> 0.1.2

GitHub release

Summary

This release updates the moduleId to a PagerDuty specific one (pagerduty-actions). The moduleId configured on the initial release (custom-extensions) conflicts with the example value from the backstage documentation for writing custom actions.

Changes

fix: use pagerduty-specific moduleId

Dependencies

@pagerduty/backstage-plugin-common: ^0.1.2

> 0.1.1

GitHub release

Summary

This release introduces a small improvement to the migration process to the new backend system. With the change introduced we made the createPagerDutyServiceAction parameters optional and therefore existing users just need to update the package reference in packages/backend/src/plugins/scaffolders.ts.

Changes

refactor: refactor to avoid additional parameters

Dependencies

@pagerduty/backstage-plugin-common: ^0.1.2

> 0.1.0

GitHub release

Summary

Version 0.1.0 of @pagerduty/backstage-plugin-scaffolder-actions represents the first release of this new Backstage backend module.

Before version 0.6.0 of @pagerduty/backstage-plugin-backend, which introduces support for Backstage's new backend system, both REST APIs and Scaffolder actions were part of the same package.

By adding support for the new backend system, we were forced to isolate the existing Scaffolder Actions in a separate package. Below are the steps to onboard this new package to your Backstage App.

For existing users using the legacy backend system

Install new package

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

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';
```

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

Install new package

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

(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

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

chore: extract scaffolder actions from @pagerduty/backstage-plugin-backend
chore(deps): Bump tar from 6.2.0 to 6.2.1

Dependencies

@pagerduty/backstage-plugin-common: ^0.1.2