Am trying to build a CI/CD pipeline for Apigee Edge on Azure Devops. Below is the requirement and what I have done so far.
Requirement:
1. Once Swagger specs are saved in swaggerhub, they need to be validated against custom rules.
2. After validation they need to be automatically imported into Apigee Edge as a basic proxy.
3. If possible this basic proxy needs to have some shared shows incorporated as well.
4. Then the dev team works on the proxy and completes development.
5. The new revision needs to be pushed into Github as a repo.
6. From the repo, the CI/CD pipeline should kick off with code analysis (Apigee bundle linter), Unit tests (postman?), Deploy (apigee-maven-plugin?), Tests (Apache Jmeter / apickli).
Note: The pipeline should support both OAS2.0 and OAS3.0.
Done so far:
Swagger specs validation is possible using a swagger-CLI tool, but API standardization within swaggerhub (available for Enterprise plans) provides inbuilt validation. Question is how to get custom rules built in.
OpenAPI2Apigee tool to import the spec into Apigee Edge has worked for me so far, as it keeps failing at the base URL.
I am trying to use curl commands to export the API proxy revision and then push it to Git to build the pipeline.
Please let me know if any of you have worked on anything similar before. If I could crack the OpenAPI2apigee tool i would have something to go on.
but the tool seems to be an interactive one, and in Azure devOps it keeps canceling the build after erroring out on the base URL.
LinkedIn
Twitter
