Setup the environment's specific env.yaml

Pre-requisites:

Git - Before you start, you have to make git available on your computer. Getting-Started-Installing-Git.
Sops - Install Mozilla sops https://github.com/mozilla/sops
KMS key - https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html
Helm - Install Helm https://helm.sh/docs/intro/install/
Domain Name - If you don’t have the domain, Please procure the domain name. ( you can procure it from GoDaddy or any other domain registrar )
Email Account - Email account for the email notification.
SMS gateway - Please get the SMS gateway (you can use https://www.smscountry.com/registration or any other SMS gateway provider)
Two s3 buckets - 1 - assets s3 bucket to keep environment specific pictures and custom-js-injection scripts. 2 - Filestore.
Payment Gateway - Payment Gateway Service
IAM user - Access and secret key to access filestore bucket. Please create and attach the IAM policy to the user. ( writing-iam-policies-how-to-grant-access-to-an-amazon-s3-bucket )

Please clone the Digit-DevOps repo and checkout to the Training-DevOps branch.
Create your environment specific file. Go to the environments folder it is in deploy-as-code/helm/environments.
- Copy and rename the existing egov-demo.yaml and egov-demo-secrets.yaml files with your environment name.

Example: pb-uat.yaml and pb-uat-secrets.yaml

Add your domain name. Replace the egov-demo.egovernments.org with your domain name.

Update the egov-config details:
- Replace the db-host, db-name ,db-url and db username, password from the env-secrets.yaml. flywayUsername and flywayPassword will be and as db username and password.
- Please also update the other values accordingly to your values, like an s3-assets-bucket name and egov-state-level-tenant-id.
- Note - assets s3 bucket name should be started from your egov-state-level-tenant-id. Example