Releases: PagerDuty/backstage-plugin
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-onlymode, 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
Contributors
Assets 2
0.9.3
Summary
This release removes the pagerDuty.apiToken and pagerDuty.oauth configuration definitions from this repository as they should be treated as secret config and this frontend plugin does not need to know about them.
These configurations will now be exclusive to the backend plugin.
Changes
- fix: remove config definitions that are secret (#78) by @alecjacobs5401
This release was made possible by the following contributors:
Contributors
Assets 2
0.9.2
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.comThis feature in mainly implemented in @pagerduty/backstage-plugin-backend but this release updates the plugin config schema accordingly.
Changes
This release was made possible by the following contributors:
Contributors
Assets 2
0.9.1
Summary
This release introduces a security patch to a third-party dependency.
Changes
- chore(deps): bump ip from 2.0.0 to 2.0.1 (#73) by @dependabot
This release was made possible by the following contributors:
@dependabot, @dependabot[bot] and @t1agob
Contributors
Assets 2
0.9.0
Summary
This release adds the type necessary for OAuth support in Backstage plugin configuration. Users can now configure the following OAuth parameters in Backstage app-config.yaml file.
pagerDuty:
oauth:
clientId: ${PD_CLIENT_ID}
clientSecret: ${PD_CLIENT_SECRET}
subDomain: ${PD_ACCOUNT_SUBDOMAIN}
region: ${PD_ACCOUNT_REGION} // Optional. allowed values: 'us', 'eu'. Defaults to 'us'.It also introduces more friendly error messages when permissions for certain APIs or operations are not present. This was implemented not to break the PagerDuty Card experience.
Changes
- feat: add suport for scoped oauth (#70) by @t1agob
- fix: update error links to pagerduty docs (#66) by @codingdiaz
This release was made possible by the following contributors:
@codingdiaz and @t1agob
Contributors
Assets 2
0.8.3
Summary
Version 0.8.3 fixes an issue that was causing an error message to show on-screen for user accounts that don't have AIOPs or Event Intelligence capabilities.
With this changes instead of getting an out-of-context error message users will see this image and message instead.
Changes
This release was made possible by the following contributors:
Contributors
Assets 2
0.8.2
Summary
Version 0.8.2 bumps the version of @pagerduty/backstage-plugin-common to version 0.0.2.
Version 0.0.1 had a misconfiguration that was forcing the backend plugin to load it as an ES6 module and while that's supported for the frontend it is not yet fully supported for backend plugins.
This dependency upgrade syncs the version of the common package between frontend and backend plugins.
Changes
This release was made possible by the following contributors:
Contributors
Assets 2
0.8.1
Summary
This minor release moves the direct REST API calls from the frontend component to the backend. Instead of leveraging the Backstage proxy to make direct API calls to PagerDuty the calls are made to the backend plugin instead.
This removes the dependency on the proxy and prevents other plugins from using the PagerDuty proxy configuration to call PagerDuty APIs directly for other purposes which raises few security concerns.
Therefore the proxy configuration for PagerDuty on app-config.yaml is no longer required and is in-fact deprecated.
Changes
- feat: migrate api calls (#59) by @t1agob
- chore(deps): bump follow-redirects from 1.15.3 to 1.15.4 (#57) by @dependabot
This release was made possible by the following contributors:
@dependabot, @dependabot[bot], @jcoelho93 and @t1agob
Contributors
Assets 2
0.7.4
Summary
This release includes a fix to a bug (#54) that prevented the PagerDutyCard from refreshing when users leveraged the Backstage search to navigate between components.
Changes
This release was made possible by the following contributors:
Contributors
Assets 2
0.7.3
Summary
This release updates the Backstage plugin configuration schema to add support for apiToken.
pagerDuty:
apiToken: u+a81u12y4axThe latest release of the backend plugin (0.2.0) required a schema change for the plugin to start successfully. It does not introduce new features or capabilities to this plugin but it makes sure that the schemas match and avoid misconfigurations.