docs/releases/v1.43.0-next.2-changelog.md
Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.43.0-next.2
0e9ec44: Introduced new streamEntities async generator method for the catalog.
Catalog API and Catalog Service now includes a streamEntities method that allows for streaming entities from the catalog.
This method is designed to handle large datasets efficiently by processing entities in a stream rather than loading them
all into memory at once. This is useful when you need to fetch a large number of entities but do not want to use pagination
or fetch all entities at once.
Example usage:
const pageStream = catalogClient.streamEntities({ pageSize: 100 }, { token });
for await (const page of pageStream) {
// Handle page of entities
for (const entity of page) {
console.log(entity);
}
}
auth frontend package0e9ec44: Introduced new streamEntities async generator method for the catalog.
Catalog API and Catalog Service now includes a streamEntities method that allows for streaming entities from the catalog.
This method is designed to handle large datasets efficiently by processing entities in a stream rather than loading them
all into memory at once. This is useful when you need to fetch a large number of entities but do not want to use pagination
or fetch all entities at once.
Example usage:
const pageStream = catalogClient.streamEntities({ pageSize: 100 }, { token });
for await (const page of pageStream) {
// Handle page of entities
for (const entity of page) {
console.log(entity);
}
}
0e9ec44: Introduced new streamEntities async generator method for the catalog.
Catalog API and Catalog Service now includes a streamEntities method that allows for streaming entities from the catalog.
This method is designed to handle large datasets efficiently by processing entities in a stream rather than loading them
all into memory at once. This is useful when you need to fetch a large number of entities but do not want to use pagination
or fetch all entities at once.
Example usage:
const pageStream = catalogClient.streamEntities({ pageSize: 100 }, { token });
for await (const page of pageStream) {
// Handle page of entities
for (const entity of page) {
console.log(entity);
}
}
BACKSTAGE_ENV for loading environment specific config filescreateRouter.auth.experimentalDynamicClientRegistration.enabled in app-config.yaml. This is highly experimental, but feedback welcome.defaultTarget on createComponentRouteRef./alpha export to the root of the package.getDefault in the kubernetesFetcherExtensionPoint had the wrong this value/.well-known/oauth-authorization-server to /.well-known/openid-configuration on auth-backend when auth.experimentalDynamicClientRegistration.enabled is enabled.backstage.io/techdocs-ref or backstage.io/techdocs-entity annotations, using the shared buildTechDocsURL helper. Also adds tests to verify both annotations and optional backstage.io/techdocs-entity-path are respected.