Skip to main content
Version: 13.x (Current)

CHANGELOG

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[2.1.4] - 2024-12-04​

Security​

  • Added SBOM and docker image sign

[2.1.3] - 2023-11-21​

### Versioning

  • Updated Node to v20
  • Dev dependencies updates

Fixed​

  • Swagger is now compliant with OpenApi specification

[2.1.2] - 17-12-2021​

Fixed​

  • REST output mode validation schema now accept also get and delete HTTP methods, so that events triggers can now be created with those methods.

[2.1.1] - 23-11-2021​

Fixed​

  • The crudStorage list function now sorts the expirations by expirationDate

[2.1.0] - 17-11-2021​

Added​

  • GET and DELETE methods added to REST outputMode
  • GET method ignores the request body, if any

Changed​

  • now the payload is not required anymore and has a default value of {}

Updated​

  • custom-plugin-lib: v4.2.0

[2.0.3] - 22-06-2021​

Added​

  • Added port parameter to specify the port for the REST call.
  • Fixed deserialization error on rest replies with status code 204 or non-JSON reply.

[2.0.2] - 2021-03-04​

Updated​

  • custom-plugin-lib: v2.3.0

[2.0.0] - 2020-10-02​

BREAKING CHANGE

  • updated custom-plugin-lib dependency to 2.0.3. The update is breaking since it's bringing up lc39 v3.x with the newer logging format.

[1.1.0]​

Added​

The service, when an expiration occurs, tries to publish based on the outputMode defined into the expiration JSON and, if the publish function fails, it simply ignores it and another publish attempt will be done at the next activation.

The risk of this behavior is an infinite loop in case of invalid output mode.

Solutions

  • Add a retries object into the expiration JSON with this format:

    ...
    ...
    "retries": {
      "maxRetriesAllowed": 2,
      "currentAttemptsNumber": 0
    },
    ...
    ...

    and increase the currentAttemptsNumber when a publish fails.

    If the currentAttemptsNumber reaches the maxRetriesAllowed, the expiration will be updated in error state, or:

    ...
    ...
    "retries": {
      "maxRetriesAllowed": 2,
      "currentAttemptsNumber": 0
    },
    "expirationStatus": {
      "id": 3,
      "description": "error"
    },
    ...
    ...

[1.0.0]​

Added​

First release of the Timer Service.

  • /schedule route added to create a new expiration
  • /abort route added to abort a pending expiration