Fredrik Adelöw

Hi! @nickboldt I see you were already added to OWNERS.md, and has admin rights to the backstage-community repo. This makes it OK to close this issue as done, right?

Hi, sorry - after the [disableDefaultProcessors config flag](https://github.com/backstage/backstage/blob/14b25217517ec9ebbe9b3f8204796a6f97e83893/plugins/catalog-backend/config.d.ts#L158) was added in https://github.com/backstage/backstage/pull/29478, this is already achievable. Closing the issue.

What issues? Under what circumstances, and onto what version of gitlab? Would be good with some details referenced

It would seem that that error should have been communicated to the client over its stream, yeah. @backstage/scaffolder-maintainers agree? I'm not sure what the "unknown path" thing means though? 🤔

The semantics of the ownership refs is that they point to things that you _claim ownership through_, NOT things that you own. The ownership refs typically contain your own user's...

I'll also add that it's an entrenched thing in Backstage, that what gets communicated across boundaries is the user's entity ref _only_, and then if the receiving end wants to...

Hm. Before approving this, let me just note that it's very much an antipattern to point to anything but the trunk (for some definition of trunk) for catalog data. Some...

Hi! I've added this to our board for discussion. You haven't been forgotten.

See [this related comment](https://github.com/backstage/backstage/pull/25419#issuecomment-2227043463). I realize this PR only targets the backend code at this point, but the follow-up question will be, how do we expose this feature to the...

Would you be able to just build and ship the actual repo that you're working in (the backstage main repo clone), instead of making a new one?