You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In second phase Eclipse Kanto is introduced. Kanto provides an unified method of communication between a cloud backend and a device, using Eclipse Hono commands in combination with Eclipse Ditto messages. The concept is described here. In a very similar way it is done with the AWS IoT Core (concept can be found here) and Azure IoT Hub (concept guide is on its way) as well.
I am curious to see how the other orchestrators solved the cloud connectivity issue and if there are similarities with this approach.
* Fix dockerfile name
* Few fixes to path and dispatch
* Add some options to git checkout
* Remove tag for now
* Use buildx for arm64 build
* Try fully using buildx
* Workflow adjustments with buildx
Does the blueprint require cloud integration? If so, what kind? Could we make it generic enough to multiple cloud providers can be used?
The text was updated successfully, but these errors were encountered: