Fredrik Adelöw

You should also be able to skip `EXISTS` checks; you should safely know the state of the database when you enter the migration

There's always `-next` releases! :) And a thing like this doesn't hurt to have on the next train for a bit to let people react to any effects it might...

@aramissennyeydd sorry this needs a rebase

remember the DCO signature on each commit!

Closing as fixed!

no time to look at this right now

Check the vale warnings!

Suggestion: Maybe this would fit best inside a `CatalogModelExtensionPoint` instead of being considered part of the processing per se? https://github.com/backstage/backstage/pull/22568

The only thing it has to do is to emit something that just vaguely resembles any entity. Basically it needs to be an object, and having `apiVersion`, `kind`, and `metadata.name`...

I dunno. Ingestion is mostly a thing that's handled by entity providers, which already are on the Processing extension point (whether that's logical or not) :) I'm still voting `CatalogModelExtensionPoint`.