Visual API Database Mapper
A new stage has been released for configuring microservices that allows you to visually map database fields to OpenAPI and then generate code in Python, Spring Boot, or .NET. This allows developers to save time in code generation.
To do this, you only need to enable the Visual Mapper stage and configure the database. Add the database connection, and it will automatically load all the database schemas and attributes. Here, we can map OpenAPI resources to other OpenAPI resources. Now we perform the mappings:
Once the mappings are complete, a new OpenAPI file will be generated with the necessary tags to use the APIgens (Spring Boot, Python – Beta, .NET). The microservice will be generated fully functional and in accordance with the best practices promoted by the APIAddicts Foundation.
Default API Briefing
A default API briefing has been created with the fields defined in this documentation: https://apiquality.io/api-briefing-2/
Redesign of the security scoring
A default API briefing has been created with the fields defined in this documentation: https://apiquality.io/api-scoring-360/
Example API
From now on, an example API is created when creating an organization with the basic steps.
New fields in the stress test execution list
The execution parameters for performance tests have been added:
- Threads
- Ramp-up
- Duration
- Test cases
The option to choose the deck version for deployment in Kong has been added.
New deployment stage in the API Market portal
The option to choose the deck version for deployment in Kong has been added.
A new stage has been added that allows the APIs to be deployed automatically in the organization’s API Market.
Now we can run the stage,
And we see how it has been automatically loaded into the CMS.
Recurring and planned steps
From now on, you can schedule the steps to run every day or plan when you want them to run. This is an option in the pipeline or in the stages.