Bug Fixes

• A bug has been fixed where an API was set back to the normal state after reaching the error state. This caused messages to be sent multiple times in some cases.

• If a node was set up with metrics but is no longer accessible, performance problems could occur.

New Features

• All variables of an API can now be deleted at once.

• When migrating to multiple targets, it is now possible to link them and make adjustments to the actions for all of them at the same time.

• Integrations can now be deactivated. No messages are sent with deactivated integrations.

• The version of the gateway is now displayed in the node details.

• The overview of Resources has been improved

  • Information from folders can now also be viewed.

  • Dependencies of resources can now be clicked to search for them.

  • The value of cluster properties is now displayed.

Changes

• Easier offline migrations between environments

  • In ‘Resources’, selected resources can now be downloaded as a ZIP. These can then be specified as the source under ‘APIs’ -> ‘Perform Migration’ -> ‘Localfile’.

• The description of the alarming feature in APIs and nodes has been improved.

• The integrations for sending messages can now be added more easily to the alarming.

• The Gateway Manager API documentation has been expanded and adapted. BREAKING CHANGES

  • It is now listed which role the user needs in order to be allowed to use an endpoint.

  • Path changed from /pipeline to environments/{id}/pipeline

  • Adjustments in success response from /migrate

    • state => mappings

    • error => result

Other changes

• Minor errors relating to the various user roles have been fixed.