Davide Bettio
Davide Bettio
Draft interfaces are a great tool but errors still may happen, and therefore they would force users to manually remove interfaces from the database when the major number is not...
Devices pairing can be disabled, but they cannot be removed. This feature is required in several different scenarios, such as removing data from devices that are not working anymore, and...
`http_post_url` was limited to http POST method. `http_url` and `http_method` have been introduced with Astarte 1.0 as a replacement, therefore `http_post_url` is deprecated and should be removed with Astarte 2.0.
Allow devices disconnection from AppEngine API by PUTting false to connect device status property.
It should be allowed to watch for events on server owned interfaces. E.g. it should be possible to watch for data going from the server to the device.
All device data handling should happen inside data updater plant. Right now some direct access to devices is happening in AppEngine API.
Sample timestamp might clash with a /timestamp endpoint. Example: ```json {"string": "aaa", "timestamp": "2017-09-30T07:10:00.000Z", "value": 1.1} ``` Starting with /v2 API object aggregated values should be grouped together into a...
/v2 API should handle OPTIONS on interfaces and paths. When OPTIONS on interface/path is used: - DELETE is reported only when allow_unset is true - POST is reported only when...
Add /v1/:realm/interfaces/:interface_name/:version endpoint to AppEngine API. This endpoint would make `astartectl` (and similar tools) code simpler.
[Astarte in 5 minutes](https://docs.astarte-platform.org/snapshot/010-astarte_in_5_minutes.html) makes the assumption that astartectl is already installed, it might be easier to newcomers explaining how to install it before starting. Bonus point: some users might...