Setup CICD pipeline

[hamzajaved-csiro]

A breakdown of this PR so its easier to review:

The CICD projects are fairly similar to what we have in existing projects so not much has changed there apart from a few things in the buildspecs.

• Base Project: Provision ECR Repo and create DocumentDb secret in Secrets Manager
• Database Project: Provision DocumentDB Cluster
• Build Project: Build Docker image and push to ECR repo
• Deploy Project: Deploy the Helm chart in the lists namespace in testing cluster

Helm Chart:

• Similar to alerts repo

CICD Project in Lists-UI folder:

• Frontend Project: Similar approach to the seedbank repo

Confluence Doco:
https://confluence.csiro.au/display/ALASD/Developer+Pipeline+-+New+Species+Lists

[hamzajaved-csiro]

The remaining issue on this branch is once the pod starts in the cluster, it attempts to connect to documentdb.
The config file has the mongodb parameters and it is stored in kube secret lists-service-config-secret in "lists" namespace.

The password for the documentdb database is stored in aws secrets manager under lists-{branch-name} i.e. lists-ci-cd in this case. username adminuser.

Debugging tips:

• If you are just making changes to the config file, you can just delete the pod e.g kubectl delete pod ala-lists-service-xxxxx and it should pick up the new changes.
• If the helm chart needs to be updated, make the changes in the git repo and rerun the pipeline.
• Alternatively, if you want to deploy the helm chart from your local machine, update the values.yaml file with the image tag and ecr repo and deploy it in the lists namespace, just a matter of preference.

[brucehyslop]

I've updated the pipeline to enable deployment of feature branches (tested on feature/cicd-pipeline branch).
I would not suggest triggering pipeline on the cicd branch because it will change the hostname of deployed resource, which is currently being used by the lists UI deployed to https://lists.test.ala.org.au