Thomas Jaeckle
Thomas Jaeckle
In #288 an alternative solution for doing multiple "modify" operations by only issuing a single DittoProtocol command was suggested: Adding a DittoProtocol command which contains several other DittoProtocol commands (as...
Currently with #889 and #895 the `/cloudevents` POST endpoint acts as "sink" only: * accepting (HTTP code 202) all successfully persisted Ditto Protocol commands * for errors (e.g. missing permissions,...
After the first part of adding a `/cloudevents` route done in #889 and PR #895 there are some follow ups: - [x] in addition to `application/json` content-type, also accept the...
## Problem statement A feature which was long on the roadmap of Eclipse Ditto (see also former GH issue #125 where previous discussions were done) is the ability to distinguish...
Delete value of a "desired" feature property once the actual "property" was set to the same value
As part of #696 the goal is to have an empty or even removed "desiredProperties" section in a feature once all desired properties were applied by a device. This can...
As part of #696 a new functionality shall be introduced in order to calculate a delta/diff/patch between the `desiredProperties` and the `properties` (or reported) state of a digital twin (thing)...
As an enhancement of #696 it should be possible via the Ditto search to find out which things have pending (not yet applied) "desiredProperties". The syntax for that could be:...
As an enhancement of #696 all remaining `desiredProperties` state selectable for a thing after implementing #700 shall be returned whenever a device reconnects to its cloud backend. For Eclipse Hono...
Following up on Ditto being able to manage arbitrary metadata with #680 it could be useful in some use cases to automatically create/inject certain metadata on each modification of a...
As an enhancement of #696 it should be possible to define in a policy that all features of a single thing are addressed in the `resources` section of the policy....