Patrik Oldsberg

We discussed this a bit more in @backstage/maintainers and settled on reverting #27850. Would anyone like to prepare a PR for that? 🙏 The reasoning is that throttling the read/processing...

@CptnFizzbin I've opened #28677, aiming to close those gaps

@greptail thinking the simplest approach is to look into `NO_PROXY` or similar patterns for your case. It doesn't scale too well to start adding this to each individual integration at...

Indeed, would be best to have the cause of the error included in the log message too, that'll tell us what's actually going wrong with the fetch. Leaving this open...

Are you getting any TypeScript error on this line? `logStream: ctx.logger`, those should not be compatible. You can use `ctx.logStream`, although that's deprecated so better do what the deprecation message...

I think having the tag chips link to the catalog index page with a prepared filter makes sense 👍

Should be simple enough to implement, but not sure if there are any hidden risks/complexities. Will defer to @backstage/scaffolder-maintainers

Moving this over to https://github.com/backstage/community-plugins, since that's where the explore plugin now lives

What domain is the `/stylesheets/main.min.css` and `/api/techdocs/.backstage/auth/v1/cookie` requests towards? The host for the cookie being `xxx-backend.company.com` is correct, since the cookie is needed for requests to the backend rather than...

@jhl0214 ah, well in that case the `xxx-backend.company.com` is just an internal detail, you should configure your `backend.baseUrl` to use `xxx.company.com` in both the frontend and backend