docs/releases/v1.4.0-next.0-changelog.md
grpcDocsApiWidget to render protoc-gen-doc generated descriptors by the grpc-docs package.KubernetesObjectsProvider with new methods, KubernetesServiceLocator now takes an Entity instead of serviceIdKubernetesObjectsProvider with new methods, KubernetesServiceLocator now takes an Entity instead of serviceId8798f8d93f: Introduces a new annotation pagerduty.com/service-id that can be used instead of the pagerduty.com/integration-key annotation.
Note: If both annotations are specified on a given Entity, then the pagerduty.com/integration-key annotation will be preferred
BREAKING The PagerDutyClient.fromConfig static method now expects a FetchApi compatible object and has been refactored to
accept 2 arguments: config and ClientApiDependencies
The PagerDutyClient now relies on a fetchApi being available to execute fetch requests.
BREAKING A new query method getServiceByEntity that is used to query for Services by either the integrationKey or serviceId
annotation values if they are defined. The integrationKey value is preferred currently over serviceId. As such, the previous
getServiceByIntegrationKey method has been removed.
BREAKING The return values for each Client query method has been changed to return an object instead of raw values.
For example, the getIncidentsByServiceId query method now returns an object in the shape of { incidents: Incident[] }
instead of just Incident[].
This same pattern goes for getChangeEventsByServiceId and getOnCallByPolicyId functions.
BREAKING All public exported types that relate to entities within PagerDuty have been prefixed with PagerDuty (e.g. ServicesResponse is now PagerDutyServicesResponse and User is now PagerDutyUser)
In addition, various enhancements/bug fixes were introduced:
PagerDutyCard component now wraps error and loading messages with an InfoCard to contain errors/messages. This enforces a consistent experience on the EntityPagefetchApi to replace standard window.fetch
3500c13a33: A new template editor has been added which is accessible via the context menu on the top right hand corner of the Create page. It allows you to load a template from a local directory, edit it with a preview, execute it in dry-run mode, and view the results. Note that the File System Access API must be supported by your browser for this to be available.
To support the new template editor the ScaffolderApi now has an optional dryRun method, which is implemented by the default ScaffolderClient.
codemirror dependencies to v6.0.0.MaterialTable with Table from core-components/v2/dry-run endpoint that allows for a synchronous dry run of a provided template. A supportsDryRun option has been added to createTemplateAction, which signals whether the action should be executed during dry runs. When enabled, the action context will have the new isDryRun property set to signal if the action is being executed during a dry run.api-report, small changes in the API responses & expose the vault baseUrl to the frontend as wellwebpack-dev-server deprecations.signOut method of the IdentityApi will now navigate the user back to the base URL of the app as indicated by the app.baseUrl config.bc87604c26: Added an explicit node-gyp dependency to the root package.json. This is to work around a bug in older versions of node-gyp that causes Python execution to fail on macOS.
You can add this workaround to your existing project by adding node-gyp as a devDependency in your root package.json file:
"devDependencies": {
+ "node-gyp": "^9.0.0"
},
integrations itself.AdrSearchResultListItemgoogle-auth-library to ^8.0.0.dcaf1cb418: Previously, the color of the Entity Context Menu (in the Entity Page Header) was hardcoded as white.
This was an issue for themes that use a header with a white background. By default, the color of the icon is now theme.palette.bursts.fontColor.
It can now also be overridden in the theme, which is only necessary if the header title, subtitle and three-dots icon need to have different colors. For example:
export function createThemeOverrides(theme: BackstageTheme): Overrides {
return {
PluginCatalogEntityContextMenu: {
button: {
color: 'blue',
},
},
...
},
...
}
Updated dependencies
integrations or only integrations without frontend visible properties (e.g., bitbucketCloud) being configured by checking integrations.github directly without attempting to load integrations.StackOverflowIcon.
HomePageStackOverflowQuestions accepts optional icon property.