v1.2.0 - Salty Grasshopper

Astarte v1.2.0 Salty Grasshopper release.

Changes since 1.1

Added

• [astarte_trigger_engine] Add trigger_name to envent payload
  and mustache template
• Add support for limiting the number of registered devices in a realm.
  Existing realms are not affected by this change.
• [astarte_realm_management_api] Allow to read realm's device registration limit
  using the /config/device_registration_limit endpoint.
• [astarte_housekeeping_api] Allow to read and set a realm's device registration
  limit using the realm fetch and update API, respectively.
• [astarte_appengine_api] Show deletion status in device details.
• [astarte_appengine_api] Add /version endpoint which returns the microservice
  application version.
• [astarte_appengine_api] Added group name decoder plug
• [astarte_realm_management_api] Add /version endpoint which returns
  the microservice application version.
• [astarte_pairing_api] Add /version endpoint which returns the microservice
  application version.
• [astarte_housekeeping_api] Add /version endpoint which returns
  the microservice application version.
• [astarte_housekeeping_api] Allow to customize the RPC call timeout with
  HOUSEKEEPING_API_RPC_TIMEOUT (default: 5 seconds).
• Add API usage metrics.
• Add support for setting the maximum datastream storage retention period in a
  realm (in seconds). Existing realms are not affected by this change.
• [astarte_housekeeping_api] Allow to read and set a realm's maximum datastream
  storage retention period using the realm fetch and update API, respectively.
• [astarte_realm_management_api] Allow to read realm's maximum datastream
  storage retention period with the /config/datastream_maximum_storage_retention
  endpoint.

Changed

• Forward port changes from release 1.1.

• [astarte_housekeeping_api] Introduce a PATCH-based API for realm update.
  The old POST-based one is deprecated.

• [astarte_housekeeping] Support the new PATCH-based API for realm update.

• Update Elixir to 1.15.7.

• Update Erlang/OTP to 26.1.

• Update container base image to Debian Bookworm.

• Container user has changed from root to nobody.

• BREAKING: incoming_introspection events display introspection as a map rather
  than a plaintext string. Revert to the old behaviour by setting
  DATA_UPDATER_PLANT_GENERATE_LEGACY_INCOMING_INTROSPECTION_EVENTS to true.
  See astarte-platform/astarte_core#77.

• BREAKING: [astarte_realm_management] do not allow installation of interfaces
  where database_retention_ttl exceeds the realm's maximum datastream storage
  retention period, if set.

  Fixed

• Forward port changes from release-1.1 (connection failure when delivering triggers is handled as an error).

v1.2.0-rc.0

First Astarte v1.2.0 release candidate.

CHANGELOG

Changes since v1.1:

Added

• [astarte_trigger_engine] Add trigger_name to envent payload and mustache template
• Add support for limiting the number of registered devices in a realm. Existing realms are not affected by this change.
• [astarte_realm_management_api] Allow to read realm's device registration limit using the /config/device_registration_limit endpoint.
• [astarte_housekeeping_api] Allow to read and set a realm's device registration limit using the realm fetch and update API, respectively.
• [astarte_appengine_api] Show deletion status in device details.
• [astarte_appengine_api] Add /version endpoint which returns the microservice application version.
• [astarte_appengine_api] Added group name decoder plug
• [astarte_realm_management_api] Add /version endpoint which returns the microservice application version.
• [astarte_pairing_api] Add /version endpoint which returns the microservice application version.
• [astarte_housekeeping_api] Add /version endpoint which returns the microservice application version.
• [astarte_housekeeping_api] Allow to customize the RPC call timeout with HOUSEKEEPING_API_RPC_TIMEOUT (default: 5 seconds).
• Add API usage metrics.
• Add support for setting the maximum datastream storage retention period in a realm (in seconds). Existing realms are not affected by this change.
• [astarte_housekeeping_api] Allow to read and set a realm's maximum datastream storage retention period using the realm fetch and update API, respectively.
• [astarte_realm_management_api] Allow to read realm's maximum datastream storage retention period with the /config/datastream_maximum_storage_retention endpoint.

Changed

• Forward port changes from release 1.1.
• [astarte_housekeeping_api] Introduce a PATCH-based API for realm update. The old POST-based one is deprecated.
• [astarte_housekeeping] Support the new PATCH-based API for realm update.
• Update Elixir to 1.15.7.
• Update Erlang/OTP to 26.1.
• Update container base image to Debian Bookworm.
• Container user has changed from root to nobody.
• BREAKING: incoming_introspection events display introspection as a map rather than a plaintext string. Revert to the old behaviour by setting DATA_UPDATER_PLANT_GENERATE_LEGACY_INCOMING_INTROSPECTION_EVENTS to true. See astarte-platform/astarte_core#77.
• BREAKING: [astarte_realm_management] do not allow installation of interfaces where database_retention_ttl exceeds the realm's maximum datastream storage retention period, if set.

v1.0.6

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

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 astarte-platform/astarte_core#95).
• Forward-port changes from release-1.0 (correctly handle server-owned data,
  bugfixes in AppEngine, Data Updater Plant and Pairing).

Changed

• [astarte_e2e] Update Elixir to 1.14.5 and Erlang/OTP to 25.3.2 (see #858).

v1.0.5

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

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

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

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

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

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.