From 39e94c2a1c7d0b369fa0628d0cbaf0404320eb1c Mon Sep 17 00:00:00 2001 From: apidesigner Date: Mon, 5 Jun 2017 10:22:45 +0000 Subject: [PATCH] Updates guides/complete-api-development.md Auto commit by GitBook Editor --- guides/complete-api-development.md | 33 ++++++++++++++++++++---------- 1 file changed, 22 insertions(+), 11 deletions(-) diff --git a/guides/complete-api-development.md b/guides/complete-api-development.md index 959232e..a025569 100644 --- a/guides/complete-api-development.md +++ b/guides/complete-api-development.md @@ -132,14 +132,25 @@ > Based on the analysis, new or changing business requirements - - Create a new branch in the VCS repository with OAS file - - Create a new project (alternative) in Apiary - - Make sure the CI/CD pipeline is still - - Set to push the OAS file to Apiary but make sure to modify the Apiary project name - - Set to run Dredd test in the CI/CD - - Modify the design (OAS file) accordingly, follow the "Design API" phase - - Follow the rules for extending and adidas API guidelines versioning policies - - Use VCS pull request (PR) to propose the change to review - - After the API Design change is verified, reviewed and approved, continue with the "Develop the API" phase - - Eventually, when the updated design is ready to be deployed for production, merge the branch to the production branch - - Follow the guide from "Expose the API using Mashery" \ No newline at end of file + 1. Create a new branch in the VCS repository with OAS file + + 1. Create a new project (alternative) in Apiary + + 1. Make sure the CI/CD pipeline is still + + 1. Set to push the OAS file to Apiary but make sure to modify the Apiary project name + + 1. Set to run Dredd test in the CI/CD + + 1. Modify the design (OAS file) accordingly, follow the "Design API" phase + + 1. Follow the rules for extending and adidas API guidelines versioning policies + + 1. Use VCS pull request (PR) to propose the change to review + + 1. After the API Design change is verified, reviewed and approved, continue with the "Develop the API" phase + + 1. Eventually, when the updated design is ready to be deployed for production, merge the branch to the production branch + + 1. Follow this guide from "Expose the API using Mashery" + \ No newline at end of file