We know about it and that is actually one of the approaches we would like to
explore: Cockpit relies heavily on JavaScript running on the client (browser)
so the REST API is definitely something that might make the Cockpit
integration more "natural". At least... I hope so.
Right now all the CIM infrastructure would be in many ways parallel to the
native D-Bus/JSON ssh-tunnelled Cockpit protocol:
https://github.com/cockpit-project/cockpit/blob/master/doc/cockpit-transport.png
The REST API might be more flexible and allow more interesting things to be
developed. (I can imagine custom UI modules, etc.)
Regards,
--
Tomáš Smetana
Platform Engineering, Red Hat