v1.0.0-alpha.1

First Astarte 1.0.0 alpha release

CHANGELOG

Fixed

• Make sure devices are eventually marked as disconnected even if they disconnect while VerneMQ is
  temporarily down (see #305).

Changed

• [appengine_api] Always return an object when GETting on object aggregated interfaces.
• Replace Conform and Distillery with Elixir native releases.
• Remove the ASTARTE_ prefix from all env variables.
• [realm_management_api] Triggers http actions are now validated.
• [realm_management_api] It is now possible to omit the device_id in a device_trigger. This is
  equivalent to passing * as device_id. The old behaviour is still supported.

Added

• [appengine_api] Add metadata to device
• [trigger_engine] Allow configuring preferred http method (such as PUT or GET)
  (see #128).
• [trigger_egnine] Add optional support to custom http headers, such as
  Authorization: Bearer ... (see #129).
• [data_updater_plant] Handle device hearbeat sent by VerneMQ plugin.
• [data_updater_plant] Deactivate Data Updaters when they don't receive messages for some time,
  freeing up resources.
• [appengine_api] Support SSL connections to RabbitMQ.
• [data_updater_plant] Support SSL connections to RabbitMQ.
• [trigger_engine] Support SSL connections to RabbitMQ.
• Default max certificate chain length to 10.
• AMQP trigger actions (publish to custom exchanges) as an alternative to http triggers actions.
• Ensure data pushed towards the device is correctly delivered when using QoS > 0.
• [realm_management_api] Allow installing device-specific and group-specific triggers. To do so,
  pass the device_id or group_name key inside the simple_trigger.
• [data_updater_plant] Add support for device-specific and group-specific triggers.
• Add support for device error triggers.