Fredrik Adelöw

I'll link this to https://github.com/backstage/backstage/pull/27901 which is starting up a similar thing for google cloudsql. To answer the question, no we hadn't planned on the specific ask, but maybe the...

Just noting here that it seems we'd be moving that file into contrib, if anything

You probably didn't want to copy the routes and translations. My initial suspicion here is that by copying the routes you ended up with duplicate "twins" of the route refs....

We do that too, but with [the dedicated processing interval](https://github.com/backstage/backstage/blob/cd88dc39fc9b17582ba595038ad9c3369e64fd46/plugins/catalog-backend/config.d.ts#L176) option. Inflexibility affects mostly us - the more we expose of the deep internals, the less we are able to...

Ah yeah, sorry the nice message that explains what to do got lost, fix for that [here](https://github.com/backstage/backstage/pull/26863). You were meant to see ``` ************************************************************************************* * You have uncommitted changes to...

Sorry for not responding sooner, not sure how this one managed to fall between the chairs 🤔 Anyway, no, no technical problem with using the `filter` approach. That's actually what...

I am not sure it should be the default. The set of users in the catalog is usually leveraged as a security mechanism. For example, signing in is usually gated...

Alright! So I thought a bit more about this one. ```yaml new FileReaderProcessor(), new UrlReaderProcessor({ reader, logger, config }), CodeOwnersProcessor.fromConfig(config, { logger, reader }), new AnnotateLocationEntityProcessor({ integrations }), ``` This...

Fixes #27352

Also mentioning here that https://github.com/backstage/backstage/pull/29740 removes the `CodeOwnersProcessor` from the defaults