Setup the environment's specific env.yaml

Pre-requisites:

Steps To Setup environment file:

  • Please clone the Digit-DevOps repo and checkout to the release 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-sample.yaml and egov-demo-sample-secrets.yaml files with your environment name.

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

  • Secrets Management using Mozilla sops - Mozilla SOPS is a cli tool to works with filetypes that relies on key:value format (json, yaml, env) and does that by **encrypting only the values**, allowing us to see the keys and thereby comprehend the set of secrets that are present on that file without leaking the values.

  • Add your domain name.

  • Update the egov-config details:

    • Replace the db-host, db-name, and db-url.

    • Upade the db username and password from the env-secrets.yaml. flywayUsername and flywayPassword would be the same 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 If your tenant id is in the assets bucket name should be in-epass-assets.

 

  • Update the filestore bucket details:

    • update the aws-key and aws-secret-key from env-secrets.yaml.

  • Repace the SMS Notification details with your SMS gateway details:

    • update the username and password from env-secrets.yaml.

 

  • Update the mail notification values from env-secrets.yaml.

  • Update the Payment Gateway details with your details.