Cumulocity IoT HTTP Request via a local API proxy

[reubenmiller]

Support the entire Cumulocity IoT REST api via a local tedge interval. This would allow components to take full advantage of the full API without having to wait for specific implementation of new API when it is introduced.

However it should not just be limited to a 1:1 proxy, there should also be some additional usability endpoints to reduce the implementation effort required for components or child devices to make use of it.

Overview

• Support Cumulocity IoT REST API to allow components to access it if there is a specific use-case for other components
• Provide common information such as managed object id or external identity of the main device and any know child devices (to reduce number of api call required)
• Create some common API endpoints which abstract a more complex sequence of c8y api calls, such as the event binary upload api.

[reubenmiller]

For example, a plugin can do the following call

PUT localhost:9000/inventory/managedObjects

Or using some child name.

PUT localhost:9000/{child01}/inventory/managedObjects

[reubenmiller]

Included in thin-edge.io 0.13.0