...

This allows the compatibility information to be refreshable since `supported.configs` can be deleted from an entity. This could be useful as clients go offline and are upgraded to clean up stale compatibility data. Clients register configs every time they request configs, so the compatibility information will eventually be added again and continuously updated as clients of different versions register configs with the entity. 

The big flaw in storing the registration alongside configs is that the entity config could be updated concurrently if multiple clients with the same entity names register at the same time. An alternative to storing the config registration statically is to store it in an internal topic and use a streams application to process it. This would allow more fine grained and accurate compatibility information to be given to the user.

Public Interfaces

...

Admin Client Changes

...