Vincenzo Scamporlino

Hi all 👋, We heard your feedback and we are in the process of rethinking/rewriting the current chart. We have a prototype here https://github.com/vinzscam/backstage-chart looking for your feedback, to understand...

> @vinzscam once this is released would you like a PR to support running a _DEV_ database in Kubernetes so the chart can be used for quick POCs? Isn't already...

you can do this in one shot using `getEntities` and filtering by name: ```javascript function fetchByRefs(refs: string[]) { const { items } = await catalogApi.getEntities({ filter: { 'metadata.name': refs.map(r =>...

> @vinzscam that will load all of the records into memory which is undesirable. then wait for #12246

> Yeah, I don't really need what #12246 brings. It'd be much simpler to do what @freben suggested, just have an endpoint that takes a list of refs and returns...

Yeah I can agree with the first point, but if we have the query string url length problem in the new hypothetical endpoint, it means we should revisit this solution...

it looks like you have two different versions of react-router, which might have generate the issue. Also one of the versions is `[email protected]` which we migrated away time ago. More...

good point @cursedcoder, let's open a PR so that we can discuss what's the best way to improve the structure of the components

yeah this is the default behaviour and it was done on purpose. I feel like the decision here is whether it makes sense to keep or remove the redirect

Hi @davidkarlsen, could you share the new issue you are getting?