Table of Contents
AI readiness scoring
From now on, a new scoring system can be calculated for APIs. To obtain it, we must enable a stage in the environments.
And to obtain it, we only need to run it
Here, a new rating will be created that we can view on the ratings screen:
Clicking on the global scoring will take us to the new dashboard:
Here, we can see the scoring for each section and its consequences:
indicating the critical issues and a roadmap for improving the API:
Default templates
From now on, when creating a new organization, a default API manager template will be created from the allowed API managers to facilitate deployment configuration.
Comments
From now on, comments will be displayed as if they were a redocly or spectral warning or error.
New openapi editor (Beta)
The new openapi editor has been updated with the following configuration:
- Show the errors
- It allows filtering by comments, redocly, or spectral
- It allows you to create comments directly by clicking on the line. Furthermore, it’s displayed differently depending on whether it’s a comment or a warning.
To display the new editor, you need to activate it in an organizational parameter:
Approval lifecycle for executing different stages
From now on, it will be possible to request the execution of certain stages (for example, for production deployments) directly from the tool.
To configure it, we will have to go to environments and select the hand icon:
Here we can configure which stages or pipeline we want to request:
Now, in the environment where we have configured the permission request, let’s go to the stages we want to run:
We now see that an email will be sent to the configured approval roles:
Here you can accept or reject the execution:
If you reject it, you must indicate the reasons for the rejection and an email will be sent to the user who made the request:
Package Executor
From now on, pipelines or stages can be executed as packages simultaneously. To do this, we can select the APIs we want:
and we configure the stages or pipelines to be executed.
The executions will be loaded in the new tab that appears on the initial screen, and we can see the status of each of the executions:
Default stage
From now on, if we want to create a new stage, a default one will be generated so that users can use it as a guide.
Apigee
Environment Setup: Completed the integration of SA configurations and environment variables.
Tooling Integration: Successfully merged the stage mixer from
apigeetemplaterandopenapi2apigee.Target Customization: Users can now configure Target Names or URLs directly via the form. Additionally, we’ve introduced an Advanced Configuration section for more granular target control.
Improvement in the Kong life cycle
The configuration URL is changed to admin URL for better understanding.
Wso2
- From now on, the environment definition file will not be deleted when performing a synchronization with Wso2.
- A new default wso2 configuration template has been added to make it easier to use as a template.
- An improvement has been added that allows you to see an error message when you run wso2 deployer and the initializer has not been executed:
IBM API Connect
- The initializer stage has been configured to overwrite files so that the stage does not fail.
- The IBM serializer has been changed to renumber fields such as Catalog or Scope.
Bugs and minor improvements
- All application windows have been enlarged to allow for increased information in the catalog tables.
- The internationalization of internal application notifications has been improved.
- A validation has been added to ensure that branches do not have spaces.
- The backward compatibility stage has been modified to check for changes every time it runs, even if the “update” command was not included in the commit.
- The configuration alert for openapi2postman stages has been removed when a global configuration has been performed.
- The names of the cards for the English translation have been changed from “opportunities” to “API briefings”
- From now on, when newman is configured to run globally, an empty folder will be generated so that postman files can be uploaded via commit.readme.md