zurnaz / serverless-gitlab-ci-example Goto Github PK

Currently stored as environmental variables during the build process but wondering there is a better way ie secrets management or better config organisation.

Puresec has a nice tool but doesn't support node 10 so will either require a downgrade on node or a pull request to upgrade it
https://github.com/puresec/puresec-cli

Consider creating a serverless package and deploy that during the deploy stages instead of rebuilding during each time

Docker images were just added based on what worked at the time.

Spend time considering if the docker images are right for the steps and replace or create docker images that suit them better.

Seems a bit too like a vanity metric but since I have lots of tests/scans already whats one more.

Haven't got a tool in mind, requires some research.

Look into reducing permissions of the deployment user/s and splitting up the various stages to multiple users.

I remember seeing some talks recommending creating separate accounts.

Hook in some domain management probably via the serverless domain plugin
https://github.com/amplify-education/serverless-domain-manager

Split between using AWS Cognito or a more generic OAuth solution