fourtheorem / slic-starter Goto Github PK

Add the ability to add currency values within entries

The default setup requires at least three accounts (cicd, stg, prod).
To enable users to get started without this barrier to entry, support and document deployment of everything to a single account.

It should be possible to deploy CICD, staging and production all in the one account.

Suggestion by @heitorlessa - add a dashboard for SLIC Starter CD by including the Pipeline Dashboard into the deployment.

See:

• https://github.com/stelligent/pipeline-dashboard
• https://stelligent.com/2017/11/16/codepipeline-dashboard/

Avoid API Keys for internal API Gateways. Instead, use AWS_IAM authorization and grant permissions to callers using IAM policies in invoking Lambdas.

Maybe worth including a security subheading in the readme including some references to CORS?

Developer References:
1 https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
2 https://serverless.com/framework/docs/providers/aws/events/apigateway#enabling-cors

Integrate Cognito support

Add the ability to add a date to a list. i.e a due date

As a checklist creator, I want to see a history of all change to a checklist (create/update/entry change), when they were changed and by whom so I see how the checklist came to be as it is.

A a SLIC Lists developer I want to see all logs for each environment in one place so I can monitor and troubleshoot quickly.

Acceptance Criteria:

1. I can view every accounts logs separately (e.g Stg, Dev, Prod)
2. I can search by service
3. I can search by log level

Explain what the list will be used for

Instead of

https://dev.sliclists.com/list/1ba05794-2b7d-488a-8336-d9165b06b2c7

use something like

https://dev.sliclists.com/list/my-first-list

https://dev.sliclists.com cannot access https://api.dev.sliclists.com currently.

API calls receive 403 No Access Control Allow Origin type error

If a due date is approaching, remind the user to fill out/revise the checklist. ie. email notification

Ability to delete user account's when finished with them

Add the ability to add numbers to entries

As a Customer Success Manager, I want to have a welcome email sent to users after they create their first checklist so that they feel rewarded for using the platform and are more likely to keep using it.

Acceptance Criteria

1. After a user creates their first checklist, they are sent a welcome email
2. The email contains a link to their first checklist
3. The email contains the name of the checklist

There is scope to reduce package size by adding webpack and getting the benefits of bundling and tree-shaking. This should be done with minimal disruption to developer flow. We also want to retain the ability to do step-through debugging locally.

@heitorlessa has a solution for this (example uses TypeScript) here: https://gist.github.com/heitorlessa/a087f4394b38562e1a0aa128386b38b8

Add automation around IAM policy checking/creation using third party tooling (e.g. Protego) to check least privileges in Lambda roles and other roles (including build and deployment roles!)

Deploy SLIC Starter from beginning, recording any issues encountered.

As a SLIC Lists developer, I want changes committed to master to be deployed to staging and production automatically so that I don't have to spend time manually deploying and I get quick feedback on the outcome of new features.

Acceptance Criteria

1. The process should run unit tests
2. The process should run integration and E2E tests
3. Every service should be deployed if its code has changed
4. No manual configuration or intervention should be required except for production approval

Ability to specify how complete a list is. e.g Progression bar, traffic light

Add npm audit / Snyk snyk.io to the build pipeline.

Feedback from the SLIC Starter internal presentation at AWS. Consider CloudMap for service discovery. https://aws.amazon.com/cloud-map/features/

User's can specify a category for their list. This may be useful for grouping similar list's etc.