Describe the bug
The PagerDuty plugin for Backstage, when configured with OAuth, requires the following scopes to work:
abilities.read // used in scaffolder only
analytics.read
escalation_policies.read
incidents.read
oncalls.read
schedules.read
services.read
services.write // used in scaffolder only
standards.read
teams.read
users.read
vendors.read // used in scaffolder only
If some of these scopes are missing (e.g. standards.read) the PagerDutyCard fails to load and causes to app to crash. This doesn't happen for all scopes as some will fail more gracefully.
To Reproduce
Steps to reproduce the behavior:
Register an Application in PagerDuty
When setting the Application Scopes select all of the ones above, except for standards.read.
Run your Backstage application
Open a Backstage entity that contains the PagerDutyCard
Expected behavior
When a required scope is missing I would expect the PagerDutyCard to fail gracefully and present a message saying which scopes are missing in the Application Registration so it can be fixed.
Screenshots
This is how we found out the problem was related to a missing scope 👇
Describe the bug The PagerDuty plugin for Backstage, when configured with OAuth, requires the following scopes to work:
If some of these scopes are missing (e.g. standards.read) the
PagerDutyCard
fails to load and causes to app to crash. This doesn't happen for all scopes as some will fail more gracefully.To Reproduce Steps to reproduce the behavior:
standards.read
.PagerDutyCard
Expected behavior When a required scope is missing I would expect the
PagerDutyCard
to fail gracefully and present a message saying which scopes are missing in the Application Registration so it can be fixed.Screenshots This is how we found out the problem was related to a missing scope 👇