API / APIGEE Gateway Interview Questions
What is Apigee CI/CD and how do you deploy proxies in a pipeline?
Apigee supports full CI/CD integration for proxy deployments using the Apigee Maven Plugin, apigeecli (the official CLI tool), and the Apigee Management API. This allows proxy bundles to be imported, deployed, and tested as part of a standard Git-based delivery pipeline.
# Method 1: apigeecli (official Google CLI tool) # Import a proxy bundle: apigeecli apis create bundle \ --name orders-proxy \ --proxy-zip ./orders-proxy.zip \ --org my-org \ --token $(gcloud auth print-access-token) # Deploy to an environment: apigeecli apis deploy \ --name orders-proxy \ --env prod \ --org my-org \ --rev 3 \ --token $(gcloud auth print-access-token) # Method 2: Apigee Management API (REST) curl -X POST \ "https://apigee.googleapis.com/v1/organizations/my-org/apis?action=import&name=orders-proxy" \ -H "Authorization: Bearer $(gcloud auth print-access-token)" \ -H "Content-Type: multipart/form-data" \ -F "file=@orders-proxy.zip" # Method 3: Maven plugin (in pom.xml) # <plugin> # <groupId>com.apigee.edge</groupId> # <artifactId>apigee-edge-maven-plugin</artifactId> # <configuration> # <org>my-org</org> # <env>prod</env> # </configuration> # </plugin> # Typical CI/CD pipeline: # 1. Developer pushes proxy to Git # 2. CI lints the proxy bundle (apigeelint) # 3. CI runs unit tests (apickli / Mocha) # 4. CI packages and deploys to test environment # 5. Integration tests run against test # 6. Manual approval gate # 7. Deploy to prod
More Related questions...