Skip to content

Requirements

Yomi Ogunyinka edited this page Jul 13, 2021 · 1 revision

Each module should have its own folder in the repository.

It should not be specific to any service or application and should be generic/vanilla and re-usable as possible.

Make sure every argument is parameterized. Do not hard code maps which may be different for other use cases (for example the lambda argument "environment"), instead create a variable map.

Add conditions where appropriate - for example S3 resources that require CORRS.. you can not add this as an option, you will need to add a condition on the resource, then add another resource to create without CORRS.

Create defaults as much as possible so we can make our stacks light. Make use of locals so we can also set conditions to determines what another value should be. This will help reduce the amount of code needed.

That being said, keep things simple, clean and easy to read/use.

DO NOT - create dependencies with the module, it should not under any circumstance link with any other module/folder in this or any other repository.

Clone this wiki locally