Thanks for your feedback!
EDIT
Environments
The design of APIs goes through several stages of development until it reaches a level of maturity that allows them to be safely exposed in a production environment. In this journey, the use of isolated environments ensures that API management practices are applied to the different development stages, with quality control through tests, ensuring more security and efficiency.
Your environments are set up and managed on the Environments page, which is found on the Manager’s main menu.
Environments can be used alongside configured teams and roles in order to create different access groups. You can define teams that have access only to their own environment, allowing environments to be independent from each and enabling different API deployment schedules and processes, with each environment having its own life cycle. See more about teams here and about roles here.
List of environments
The Environments screen displays the list of existing environments.
The list exhibits the environment’s name, URL, the type of security configured for it (either none, TLS or mTLS) and the ACTIONS column, with icons to edit (
) and delete (
) the environment.
| The security type that is displayed on the list (either none, TLS or mTLS) isn’t configured on the Environments screen, but on Inbound Address. |
You can also filter environments by using the search field, with an autocomplete function for the information of existing environments.
Share your suggestions with us!
Click here and then [+ Submit idea]