Astarte Versions Save

Core Astarte Repository

v1.0.6

3 weeks ago

Sixth Astarte 1.0 maintenance release.

CHANGELOG

Changes since v1.0.5:

Fixed

  • [astarte_appengine_api] Allow to send binaryblobarrays over server owned interfaces.
  • [astarte_appengine_api] Doubles and DoubleArrays without decimal part are no longer saved as integer, but a trailing zero is added.
  • [astarte_data_updater_plant] Do not crash when receiving a malformed purge properties message.
  • [astarte_pairing_api] Gracefully handle HTTP requests with malformed payload.
  • [astarte_housekeeping_api] Gracefully handle HTTP requests with malformed payload.
  • [astarte_realm_management_api] Gracefully handle HTTP requests with malformed payload.
  • [astarte_appengine_api] Expose exchanged_bytes metrics as sum (instead of counter).
  • [astarte_pairing] Do not reset total sent messages/bytes when re-registering a device. Fix #776.

v1.1.1

6 months ago

First Astarte 1.1 maintenance release.

CHANGELOG

Changes since v1.1.0:

Fixed

  • [astarte_data_updater_plant] Don't crash when retrieving the interface version in a device whose introspection is empty, allowing data in astarte-data_ AMQP queues to flow seamlessy.
  • [astarte_appengine_api] Don't crash when retrieving the interface version in a device whose introspection is empty.
  • [astarte_appengine_api] Return the number of results specified by downsample_to when there are more samples than the default query limit. Fix #824.
  • [astarte_appengine_api] Return the number of results specified by downsample_to when used in combination with format=disjoint_tables. Fix #149.
  • [astarte-realm_management] Do not crash when some synchronous operations (e.g. interface install) succeed.
  • [astarte_data_updater_plant] Don't crash when handling incoming binaryblob values (see https://github.com/astarte-platform/astarte_core/issues/95).
  • Forward-port changes from release-1.0 (correctly handle server-owned data, bugfixes in AppEngine, Data Updater Plant and Pairing).

Changed

v1.0.5

7 months ago

Fifth Astarte 1.0 maintenance release.

CHANGELOG

Changes since v1.0.4:

Fixed

  • [astarte_appengine_api] Correctly handle binaryblob and datetime in server-owned object aggregated interfaces.
  • [astarte_appengine_api] Handle non-array values POSTed to an array endpoint gracefully instead of crashing with an Internal Server Error
  • [astarte_appengine_api] Handle updates of objects with invalid keys gracefully instead of crashing with an Internal Server Error.
  • [astarte_appengine_api] Return the number of results specified by downsample_to when there are more samples than the default query limit. Fix #824.
  • [astarte_appengine_api] Return the number of results specified by downsample_to when used in combination with format=disjoint_tables. Fix #149.
  • [astarte_appengine_api] Fix log noise with cassandra during health checks. Fix #817.
  • [astarte_pairing] Fix crash when using a custom CA certificate.
  • [astarte_data_updater_plant] Remove asynchronous startup of Data Updater, which could lead to Data Updater stalling in some corner cases.

Changed

  • [doc] Update the documentation structure. Pages dealing with administrative tasks involving the Astarte Operator and Kubernetes are moved to the astarte-kubernetes-operator repository.

v1.1.0

10 months ago

Astarte v1.1.0 release.

Changes Since v1.0

Added

  • [astarte_data_updater_plant] Add support for device introspection triggers.
  • [astarte_realm_management] Add support for device introspection triggers.
  • [astarte_realm_management_api] Add support for device introspection triggers.
  • [astarte_realm_management] Add support for delivery policies for HTTP triggers.
  • [astarte_realm_management_api] Add support for delivery policies for HTTP triggers.
  • [astarte_data_updater_plant] Add a HTTP trigger routing mechanism based on trigger policies.
  • [astarte_trigger_engine] Add a customizable HTTP trigger redelivery mechanism via trigger policies (see #554).

Changed

  • Update Elixir to 1.14.5 and Erlang/OTP to 25.3.2.
  • [astarte_data_updater_plant] Use the internal event type for Astarte internal messages. (e.g. device heartbeat).

Fixed

  • [astarte_trigger_engine] Allow to decode events that do not contain the deprecated version field.
  • [astarte_realm_management_api] Provide detailed feedback when a trigger action is malformed. Fix #748.
  • [astarte_realm_management_api] Include the policy field when a trigger is returned.
  • [astarte_appengine_api] Return empty data instead of error when querying properties interfaces which are not fully populated. Fix 531.

v1.1.0-rc.0

11 months ago

First Astarte v1.1.0 release candidate.

CHANGELOG

Changed

  • Update Elixir to 1.14.5 and Erlang/OTP to 25.3.2.
  • [astarte_data_updater_plant] Use the internal event type for Astarte internal messages. (e.g. device heartbeat).

Fixed

  • [astarte_realm_management_api] Provide detailed feedback when a trigger action is malformed. Fix #748.
  • [astarte_realm_management_api] Include the policy field when a trigger is returned.

v1.1.0-alpha.0

1 year ago

First Astarte 1.1 alpha release.

CHANGELOG

Added

  • [astarte_data_updater_plant] Add support for device introspection triggers.
  • [astarte_realm_management] Add support for device introspection triggers.
  • [astarte_realm_management_api] Add support for device introspection triggers.
  • [astarte_realm_management] Add support for delivery policies for HTTP triggers.
  • [astarte_realm_management_api] Add support for delivery policies for HTTP triggers.
  • [astarte_data_updater_plant] Add a HTTP trigger routing mechanism based on trigger policies.
  • [astarte_trigger_engine] Add a customizable HTTP trigger redelivery mechanism via trigger policies (see #554).

Fixed

  • [astarte_appengine_api] Return empty data instead of error when querying properties interfaces which are not fully populated. Fix 531.

v1.0.4

1 year ago

Fourth Astarte 1.0 maintenance release.

CHANGELOG

Changes since v1.0.3:

Changed

  • [astarte_appengine_api] Check for device existence before accepting a watch request on Astarte rooms.
  • [astarte_data_updater_plant] Check for device existence before installation or deletion of volatile triggers.

v1.0.3

1 year ago

Third Astarte 1.0 maintenance release.

CHANGELOG

Changes since v1.0.2:

Fixed

  • [astarte_appengine_api] Consider allow_bigintegers and allow_safe_bigintegers params when querying the root of individual datastream / properties interfaces. Fix #630.
  • [astarte_appengine_api] Correctly return 405 "Cannot write to device owned resource" when POSTing on device-owned interfaces. Fix #264.
  • [astarte_appengine_api] Correctly return 405 "Cannot write to read-only resource" when POSTing on incomplete paths of server-owned interfaces.
  • [astarte_e2e] Fix ssl options handling so that the e2e client is aware of the CA.

Changed

  • [doc] Administrator Guide: bump cert-manager dependency to v1.7.0.
  • [data_updater_plant] Increase the declare_exchange timeout to 60 sec.
  • [data_updater_plant] Increase the publish timeout to 60 sec for the AMQPEventsProducer.
  • [astarte_realm_management_api] Do not crash when receiving trigger errors. Fix 683.
  • [astarte_e2e] Allow setting custom subjects for alerting emails.
  • [astarte_e2e] Group in a single thread emails referencing the same failure_id.
  • [astarte_appengine_api] Make property unset succeed independently of whether a device session exists on the broker or not. Fix #640.
  • [astarte_data_updater_plant] Log the base64-encoded object when receiving an object with unexpected key.

v1.0.2

2 years ago

Second Astarte 1.0 maintenance release.

CHANGELOG

Changes since v1.0.1:

Added

  • [realm_management] Accept retention and expiry updates when updating the minor version of an interface.
  • [astarte_realm_management_api] Allow synchronous requests for interface creation, update and deletion using the async_operation option. Default to async calls.
  • [astarte_housekeeping_api] Allow synchronous requests for realm creation and deletion using the async_operation option. Default to async calls.

Fixed

  • [realm_management] Accept allowed mapping updates in object aggregated interfaces without crashing.
  • [astarte_appengine_api] Handle server owned datetimearray values correctly.

Changed

  • [astarte_housekeeping] Allow to delete a realm only if all its devices are disconnected. Realm deletion can still only be enabled with an environment variable (defaults to disabled).
  • Update CA store to 2022-03-21 version.

v1.0.1

2 years ago

First Astarte 1.0 maintenance release.

CHANGELOG

Changes since v1.0.0:

Added

  • [data_updater_plant] Add handle_data duration metric.
  • [doc] Add documentation for AstarteDefaultIngress.
  • [doc] Add deprecation notice for AstarteVoyagerIngress.
  • [doc] Add documentation for the handling of Astarte certificates.

Changed

  • [doc] Remove astartectl profiles from the possible deployment alternatives.

Fixed

  • [astarte_appengine_api] Correctly serialize events containing datetime and array values.
  • [astarte_appengine_api] Do not fail when querying datastream interfaces data with since, to, sinceAfter params if result is empty. Fix #552.
  • [astarte_appengine_api] Consider microseconds when using timestamps. Fix #620.
  • [astarte_appengine_api] Don't crash when removing an alias with non-existing tag. Fix 495.
  • [astarte_trigger_engine] Correctly serialize events containing datetime and array values.
  • [astarte_data_updater_plant] Don't crash when receiving binaryblobarray and datetimearray values.
  • Update Cyanide BSON library, in order to fix crash when handling ill-formed BSON arrays.