CI/CD for API Proxies -- How to enable Continuous Integration/Delivery as API Proxies are in Configuration Files

Google Cloud Apigee
1

Hi all, I like to enable true CI/CD for API Proxies – But currently everyone is developing the API Proxies in the web browser, downloading the API Proxies and uploading it to SCM.

Is there some way to enable true, true Continuous Integration/Delivery as API Proxies are in Configuration Files not code?

Where one builds in an IDE, commit the code to the SCM and it gets deployed? Instead of building in the web browser, downloading the API Proxies revision and committing the code manually.

Thank you.

Regards,

Nathan Aw

2

There are Maven plugins that enable you to have a build process that can deploy API proxies, shared flows, other configuration such as KVM, etc

https://github.com/apigee/apigee-deploy-maven-plugin

https://github.com/apigee/apigee-config-maven-plugin

There’s an example Docker container that provides a Jenkins instance with these plugins getting used as part of a build process for an API Proxy

https://github.com/apigee/maven-jenkins-ci-demo