1 year ago

How do you prevent the most common merge conflicts when your team is working on a Serverless application? You can use https://www.npmjs.com/package/cfn-include and https://www.npmjs.com/package/swagger-cli to organize, collaborate, and maintain a large serverless application as well as support a large or decentralized development team.

Eliminate potential merge issues for files that generate the most conflicts during the development of a typical Serverless API application.

This will result in a highly-organized directory structure, as seen in the sample project: ├── api │ ├── apiSkeleton.yaml │ ├── fields │ │ ├── color.yaml │ │ ├── metadata │ │ │ ├── count.yaml │ │ │ ├── message.yaml │ │ └── widgetname.yaml │ ├── gatewayResponses │ │ ├── error.yaml │ │ └── notFound.yaml │ ├── paths │ │ ├── reports │ │ │ ├── reportsColor.yaml │ │ │ └── reportsFilterPage.yaml │ │ └── widget │ │ ├── widgetPut.yaml │ │ └── widgetWidgetnameGet.yaml

For example: ├── cloudformation │ ├── resources │ │ ├── apigw │ │ │ └── widgetApiGW.yaml │ │ ├── dynamodb │ │ │ └── widgetDdbTable.yaml │ │ └── lambda │ │ ├── layers │ │ │ └── lambdaDDBEnv.yaml │ │ ├── reports │ │ │ ├── reportsColorLambda.yaml │ │ │ └── reportsColorLambdaRole.yaml │ │ └── widget │ │ ├── widgetGetLambda.yaml │ │ └── widgetGetLambdaRole.yaml │ └── templateSkeleton.yaml