...

The user should be able to see what dynamic configs are supported for each application. However, clients may not necessarily support the same dynamic configs even if they are using the same <user, client-id> entity. A solution to this is to store a map of client software names and versions to lists of supported configs in each <user, client-id> entity config. The producer and consumer clients can register the configs they they support and the broker can tie the registered keys to the serialized ClientInformation from the RequestContext so that this compatibility information can be displayed to the user. As long as the user knows what version of client each application is using, they will know which applications will be effected affected by each dynamic config.

A dynamic client config supported.configs can be added to hold the value of this config which will be a JSON of what is described above. 

This

...

makes the compatibility information refreshable since `supported.configs` can be deleted from an entity. Clients register configs every time they request configs, so the compatibility information will eventually be added again and continuously updated as new clients associate themselves with the entity.

Public Interfaces

...

Admin Client Changes

...