Date of version: June 7, 2023

This document contains New Features, Important Enhancements, Modifications and Bug Fixes for version 2023.06.1.

New Features

APNZ-3607 Manual Kubernetes Management

Previously, the definition and management of Gateway and Cache servers on Kubernetes were done through Apinizer by default. With this version, the manual management of existing Kubernetes clusters is now possible by simply performing the relevant metadata configurations. As a result, the requirement to manage Kubernetes environments through the Apinizer management console has become optional. See.

APNZ-3626 Personal API Access Token Creation

A Personal API Access Token is a token used to authenticate the user's identity instead of a password during access to Apinizer Management API. It can be generated via Authorization API or "my profile page" at management console. See.

APNZ-3629 Restoring API Proxy Based on Deployment History

The API Proxy can be restored to a previous revision (deployed state) using the API Proxy deployment history. See.

Important Enhancements and Modifications

APNZ-3566 Enhanced user experience for date filtering fields in screens displaying job results.

APNZ-3620 Improved user experience for the General Settings screen.

APNZ-3633 Introduced the ability to add a new API Proxy if it does not exist, or update an existing one, through the API Proxy save and update methods in ApiOps.

APNZ-3649 In the ApiOps API, after saving/updating an API Proxy, the option to deploy it and configure routing information is now available.

Bug Fixes

Issue No	Description
APNZ-3434	Fixed an issue where the pod status was not being updated when the environment information was updated.
APNZ-3602	Resolved an issue where deleting the API Proxy resulted in the deletion of all associated monitor information, but scheduled jobs were not being unscheduled.
APNZ-3608	Fixed a problem where the error message related to the database connection was not being displayed correctly when making a request to the API Proxy created with DB2API.
APNZ-3636	Fixed the API Traffic logs to correctly display the last visited address when there are multiple routing addresses instead of always showing the first address.