Fredrik Adelöw

For anyone following along: We had a chat on discord about some of the details here. It's unfortunate that the upstream service in this case is causing undesired complexity by...

Yep sure, I'll take a look!

To clarify: The catalog backend absolutely does not allow two output entities to have the same ref (`kind:namespace/name` triplet). That's enforced by a database uniqueness constraint and is a hard...

I'll also add that checking things (at a cost) during registration isn't a problem. That happens only once every now and then. But performing complex large-scope sweeping validation in the...

Yeah agreed. The _backend part_ of the analysis only looks at the entity body and sees that it's OK and reports that back to the frontend - because the backend...

Thanks. > 1. Are there any specific guidelines or criteria for feature contributions that we should be aware of? Not much. We are fairly lax and open and there's a...

Hi! Thanks for waiting. We discussed it briefly and the consensus is: - The suggestion as such makes sense. Attaching an _optional_ lifecycle value to resources is useful and has...

I still wonder if it's possible to achieve the same with for example [theme nesting](https://v4.mui.com/styles/advanced/#theme-nesting) as per the docs, where you override only the card properties part of the theme.

It does seem like the original entity still lingers in the system, even though the unregister step happened. I'm curious: after the initial registration from GitHub, did the entity seem...

Do you happen to have the unprocessed entities plugin installed? Does it show anything for this entity? https://github.com/backstage/backstage/tree/master/plugins/catalog-backend-module-unprocessed