...
Create git branches right inside of the API Gateway Manager. There is no need anymore to create a branch in the git repository before pushing changed services. This makes it much easier to work in a feature branch workflow.
The colors for the environments can now be chosen by using a full fledged color picker. Label colors are chosen automatically based on the chosen color. The color is now shown at more places, making it easy to keep your environments apart from each other.
Backward compatible changes to the APIIDA Enhanced Format. The version attribute is stripped before pushing ressources to a git repository. The folder structure on the gateway is replicated in the repository as well in the policies directory. Services have been split up. The metadata is put into a Services.xml file in the conf directory, while the raw policy XML is put in the policies directory. This way you can make changes to your policies right in the policy XML.
Clicking on the alarm icon in the top bar, no shows a quick overview of the current alarms with the possibility to confirm those right from this drop down. A click on “show all” brings you to the alarm overview you are used to from earlier versions.
You can now protect an environment. Protected environments will have the user to reenter his password when trying to migrate to such an environment. This makes sure, that no changes are pushed to a production environment by accident. When using the API, the check is skipped as migrations using the API usually are carried out by automations without the possibility for a user to chip in and confirm the action.
You can now configure the deployment type of an environment. You can choose between Virtual Appliance / MySQL-backed Container Gateways that use Restman for migrations and Ephemeral Container Gateways, that don’t have any dependencies and are migrated by creating and updated Docker images. You can even mix both deployment types within your Gateway Manager Installation in case you run both deployment types in parallel. Ephemeral Container Gateways have a lot of advantages and you can now use the API Gateway Manager to create and provision them. All features for MySQL-backed gateways are available including all of the advanced mapping and staging capabilites of the Gateway Manager as well as the ressource explorer and the Advisor feature. Docker image defintions can either by be built and pushed to a Docker registry or they can be pushed into a git repository to run a CI/CD pipeline taking care of testing and deploying.
We can now access the ssg/ping endpoint if it is accessible and read all the information available their. This enables the API Gateway Manager to read the replication delay of the MySQL cluster backing the gateway and examining the patch level of the gateway itself.
Manual mapping of elements is now supported. Using this feature you can map different elements to each other by selecting them within a list of candidates.
...