Source: dzone.com
Promoting APIs and API Implementations to Higher Environments
Working with several customers and one major hurdle several occasions i.e. promoting API to upper environment.
Using DevOps for the deployment of: And other assets that are required in environments (Staging, Production, etc)., Anypoint Platform favors the promotion of the Anypoint API Manager definition for an API instance from one environment to another i.e. , between environments.
Promoting all supported parts of the Anypoint API Manager entry for an API instance does not copy API clients (client applications) to the target environment.
An API instance in Anypoint API Manager, the newly created/promoted API instance shares the "Implementation URL" and "Consumer endpoint" with the original API instance: this is not realistic and must typically be changed after promotion, such that, e.g., the Production API instance uses Production URLs.
Hope it would help to understand a set approach to follow in API promotion in the Anypoint platform.
Using DevOps for the deployment of: And other assets that are required in environments (Staging, Production, etc)., Anypoint Platform favors the promotion of the Anypoint API Manager definition for an API instance from one environment to another i.e. , between environments.
Promoting all supported parts of the Anypoint API Manager entry for an API instance does not copy API clients (client applications) to the target environment.
An API instance in Anypoint API Manager, the newly created/promoted API instance shares the "Implementation URL" and "Consumer endpoint" with the original API instance: this is not realistic and must typically be changed after promotion, such that, e.g., the Production API instance uses Production URLs.
Hope it would help to understand a set approach to follow in API promotion in the Anypoint platform.
Related Articles
Community Partners
DevOps Careers