Release notes v2.30 api organization scoring

API Organization scoring dashboard

The API Scoring dashboard has changed and is now as follows:

api organization scoring dashboard

Design using AI with model focus

The API Discover screen has been redesigned for model-centric design. This is the first version to enhance the use of common schemas that can also be used by AI.

 

To use this methodology, you need to create an API briefing template whose spec property is of type “path” and the type is of type form.

Now, in the list of API briefings, you can create an API briefing.

We can specify the schema, the path, and the operations.

You can create as many resources as needed, up to 2 levels.

Once we save and log back in, we can generate the API. After generating, the following API will be created:

Redesign of the API info screen

From now on, the API display screen has been redesigned to include deployment information and scoring.

APIOps Example

From now on, you will be able to create a new sample API with the complete sample lifecycle.

When creating a new organization:

A new API will be created with an example API briefing along with an API briefing template.

We can specify the schema, the path, and the operations.

Display execution parameters in performance tests

From now on, you will be able to see the parameters for threads, ramp, duration, and test cases in each performance test run.

Visual Mapper

The APIAddicts Foundation’s visual mapper has been integrated.

With the Visual Mapper, you can easily map OpenAPI to the database and use the Foundation’s APIgen to generate fully functional microservices in Spring Boot, .NET, and Python that adhere to the Foundation’s best practices. For more information, please visit the following URL:https://github.com/apiaddicts

Modified stage icon

From now on, an icon will be displayed to indicate that the stage has been modified.

Bus and little features

  • The deck version has been added to the Kong deployment
    A field has been added to the properties to indicate whether or not it is visible in the devportal for Wso2
  • The apiquality tags have been added so that the tags are displayed in wso2 api manager
  • The deployment stages for Apigee have been created on Bitbucket,
  • It has been verified that repeated values ​​are not allowed in the wso2 configuration yaml

Leave a Comment

Your email address will not be published. Required fields are marked *