Bug Fixes

• If a library's resources were only available in git, they were not found in the migration overview and could not be compared with the resources of the target.

• Charts on the dashboard sometimes behaved strangely when they had no content.

• The information and versions of the solution kits in Node -> Information are displayed correctly again.

• If a node was completely empty, an error message was displayed when checking the connection.

New Features

• Advanced certificate management

  • Certificates from the Trust Store as well as user certificates from the identity providers are now displayed here.

  • This overview includes the expiration date, the fingerprint and much more.

  • These certificates can be deleted, created or replaced individually or simultaneously on selected nodes.

  • The new advanced certificate management can be found under Node -> Security.

• It is now possible to repeat a migration via the Gateway Manager API.

  • More information can be found in the API documentation of your Gateway Manager instance.

    • https://apiida.atlassian.net/wiki/x/BoDuJgE

• Overwriting the default action of the migration mappings is now possible with regular expressions.

  • These regular expressions can be managed in https://apiida.atlassian.net/wiki/x/-ACDWw , but can also be passed as parameters via the API for a single migration.

  • This extension is available for /apis/{id}/migrate, /apis/{id}/migrateAsync and /migrate see API Documentation for more details.

    • REST API | Open API Documentation

• APIs can now be marked as favorite.

  • As a result, these APIs are displayed at the top of the API overview, as well as in the selection boxes.

  • In the overview of the APIs, there are also filters and markers:

    • Favorite API

    • Managed by API Control Plane

    • Version Control set up (git)

Changes

• The phrase “Skip Indexing” is replaced by “Skip Reload” and the explanatory text is adapted:

  • Before each migration, all required resources are retrieved again from the specified source and target. If the gateway is managed exclusively by this API Gateway Manager instance or you know that all resources are up-to-date, this step can be skipped.

  • The default behavior can be set in the configuration in General.

• Interaction and display of nodes in clusters

  • It is now displayed which of the nodes is the primary node and is therefore used for communication with the cluster.

  • The tabs displayed within a node or cluster are now only displayed if this makes sense.

    • For example, you can click “discover APIs” directly in the cluster, but the tab for migrations is only available in the cluster or in the primary node.

  • The information panel on the right-hand side within a cluster or node now contains more and more useful information.