@pagerduty/backstage-plugin-entity-processor 0.1.0-next.0 → 0.1.0-next.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +5 -7
  2. package/package.json +2 -5
package/README.md CHANGED
@@ -7,12 +7,11 @@
7
7
  **Bring the power of PagerDuty to Backstage!**
8
8
  The PagerDuty plugin reduces the cognitive load on developers responsible for maintaining services in production. Instead of having to go to PagerDuty's console, you can now access the necessary information directly within Backstage. This includes finding active incidents or opening a new incident, reviewing recent changes made to the service, and checking who is on-call.
9
9
 
10
- The PagerDuty Scaffolder Actions package allows users to create services in PagerDuty directly from their Software Templates in a single step by leveraging the `pagerduty:service:create` custom action.
10
+ The PagerDuty Entity Processor package allows users to map their existing PagerDuty services to existing Backstage entities by leveraging point and click instead of updating all configuration files on every single service. With this we want to ease the path for existing PagerDuty customers to integrate easily with Backstage and smoothly transition to a configuration based approach.
11
11
 
12
12
  ## Features
13
13
 
14
- - **Scaffolder Action for creating services** This feature enables teams to create project templates that automatically generate a corresponding service in PagerDuty. These services come with a built-in integration to Backstage, which conveniently configures the frontend plugin for your service.
15
-
14
+ - **Entity processor** This feature augments Backstage entities with the appropiate PagerDuty annotations to allow easy mapping between Backstage entities and existing PagerDuty services.
16
15
 
17
16
  ## Getting Started
18
17
 
@@ -25,18 +24,17 @@ The installation of the PagerDuty plugin for Backstage is done with *yarn* as al
25
24
  To install this plugin run the following command from the Backstage root folder.
26
25
 
27
26
  ```bash
28
- yarn add --cwd packages/backend @pagerduty/backstage-plugin-scaffolder-actions @pagerduty/backstage-plugin-common
27
+ yarn add --cwd packages/backend @pagerduty/backstage-plugin-entity-processor
29
28
  ```
30
29
 
31
30
  ### Configuration
32
31
 
33
- To use the custom actions as part of your custom project templates follow the instructions on the `Create PagerDuty service with Software Templates` section of the project's documentation [here](https://pagerduty.github.io/backstage-plugin-docs/advanced/create-service-software-template/).
32
+ ...
34
33
 
35
34
  ## Support
36
35
 
37
- If you need help with this plugin, please open an issue in [GitHub](https://github.com/PagerDuty/backstage-plugin-scaffolder-actions), reach out on the [Backstage Discord server](https://discord.gg/backstage-687207715902193673) or [PagerDuty's community forum](https://community.pagerduty.com).
36
+ If you need help with this plugin, please open an issue in [GitHub](https://github.com/PagerDuty/backstage-plugin-entity-provider), reach out on the [Backstage Discord server](https://discord.gg/backstage-687207715902193673) or [PagerDuty's community forum](https://community.pagerduty.com).
38
37
 
39
38
  ## Contributing
40
39
 
41
40
  If you are interested in contributing to this project, please refer to our [Contributing Guidelines](https://github.com/PagerDuty/backstage-plugin-backend/blob/main/CONTRIBUTING.md).
42
-
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pagerduty/backstage-plugin-entity-processor",
3
- "version": "0.1.0-next.0",
3
+ "version": "0.1.0-next.1",
4
4
  "main": "dist/index.cjs.js",
5
5
  "types": "dist/index.d.ts",
6
6
  "license": "Apache-2.0",
@@ -27,18 +27,15 @@
27
27
  "@backstage/backend-plugin-api": "^0.6.16",
28
28
  "@backstage/config": "^1.2.0",
29
29
  "@backstage/plugin-catalog-node": "^1.12.2",
30
+ "@pagerduty/backstage-plugin-common": "^0.1.4",
30
31
  "@rjsf/core": "^5.14.3",
31
32
  "node-fetch": "^2.6.7",
32
33
  "winston": "^3.2.1",
33
34
  "yn": "^4.0.0",
34
35
  "zod": "^3.22.4"
35
36
  },
36
- "peerDependencies": {
37
- "@pagerduty/backstage-plugin-common": "^0.1.4"
38
- },
39
37
  "devDependencies": {
40
38
  "@backstage/cli": "^0.24.0",
41
- "@pagerduty/backstage-plugin-common": "^0.1.4",
42
39
  "@types/node": "^20.9.2",
43
40
  "@types/node-fetch": "2.6.11",
44
41
  "@types/supertest": "^2.0.12",