Creating some templates will help future collaboration with this simple project

More documentation is needed:

• What this project is
• How it works
• How to run it
• Licenses and Contributing Policies

There should be a stage in the middle of the pipeline run, which can be turned on an off by terraform variables, which enables manual approval, meaning it can only be deployed to service catalog once the manual approval has gone past

Many of the resources are either using default names (Helpful as they are unique) which now should be changed to a uniform name, and a potential suffix can be added to all of them to allow for multiple unique pipelines running in parallel to exist.

Add a Github Action to the repo which scans all the comments and Documentation for spelling mistakes.

This is helpful for anyone contributing who may not notice small mistakes in their spelling, but can make a big difference in the documentation.

This should run every push to the repo.

Add a variable that allows you to pass in a custom buildspec yaml file which will be read in the build stage of the pipeline. This allows people to add their own custom tests on top of the cfn-lint that it already does.

At the end of the pipeline, there should be a stage where it gets deployed to service catalog. This should add new versions when the template is updated, rather than overwriting existing versions.

Tags should be an optional variable accepted by the module allowing for users to be able to tag the infrastructure as needed.

We need a stage in the run which runs static analysis such as formatting and linting on the template file. This will allow some quick errors to show up early on in the run

Adding some github actions to the repo.

Static analysis such as:
Terraform Linting
Cloud Formation Linting
Go Linting

Then some documentation linting would be handy that would help check for spelling mistakes

The deploy role in ./module/iam should not have admin access. This role should be audited to have the least amount of permissions, then the role arn should be returned to the user, where they can then add added permissions if they would like

Currently the approval stage is mandatory, we need it optional so people can choose full automatic deployments if the approval is declared elsewhere.