Patrik Oldsberg

@msamad ah alright, I think #639 is a better fit for that train of thought. This RFC is targeting specifically catalog integrations.

@msamad yep, I think the endpoint proposed by this RFC will let you detect all of those things, but as you say something like #639 would have to be used...

> What worries me is the producer implementation, which might need some precautions that could affect performances. One of the assumptions (already mentioned above) of this proposal is that the...

Closed #10115 for us to focus elsewhere, but it remains my suggested way forward for a simple but reliable change notification stream if we want to add that.

I'm implementation of this is more or less done in #10115, although that is a bit old by now. Without having thought too much about the impact I think it...

@danangarbansa thanks! How do you envision the reader to be implemented? Would it be polling the full entities endpoint and manually figure out changes or something like that? It's important...

@grantila how would you structure that though? We can't reference `BackstageCredentials` in a common package but want to keep things type safe

@kuangp not gonna go out in the next release but might have it ready for 1.32

@pjungermann the `EventParams` -> `Event` change is a pretty tricky one, in particular due to the `subscribe` callback currently giving you `EventParams` and `EventParams | Event` doesn't really work there....

Thank you for the reviews! 🙏 This should now be ready for another round / shipping