DIGIT-2.9LTS-URBAN - birth-death-services db-migration not working in the default setup

[subhashchandrab]

Deployed the DIGIT Platform with helmfile approach(as per the doc https://core.digit.org/guides/installation-guide/digit-deployment/full-deployment-beta) and followed all the bootstrap steps. Used the postgresql from kubernetes(by enabling the built-in helm chart) and the default database postgres. In this setup, I noticed that the db-migration container logic is not working properly. If we inspect the logs of the db-migration container of birth-death-services, it shows only the below.

k logs birth-death-services-8f49b84df-566jr -c db-migration -n egov

the baseurl : jdbc:postgresql://postgresql.backbone:5432/postgres
the schemas : 

After noticing the logic in https://github.com/egovernments/URBAN/blob/urban_v2.9/birth-death-services/src/main/resources/db/migrate.sh, I realized that without passing the environment variable SCHEMA_NAME, the db migration is not executing in the default setup.

In the k8s hosted postgres, the default database name is posgtgres and below is the configuration in env.yaml file

configmaps:
  egov-config:
    data:
      db-host: "postgresql.backbone" ## Add db-host name eg: egov-demo.database.azure.co
      db-name: "postgres" ## Add db-name
      db-url: "jdbc:postgresql://postgresql.backbone:5432/postgres" 

Noticed the similar behavior in other services like hrms as well.
The helm charts have the below condition. Just wanted to understand whether the default helm chart values are meant to work with k8s hosted postgres automatically or do we need to update the values.

        {{- if index .Values "bnd-ismultischema-enabled" }}        
        - name: SCHEMA_NAME
          value: {{ index .Values "bnd-schemas" | quote }}
        {{- end }}

Are we expected to create a schema upfront and pass the name as SCHEMA_NAME for the db-migration init container to successfully execute?

[vinothrallapalli-eGov]

@subhashchandrab Please apply this fix and and then redeploy the services which are failing due to flyway issue.

[subhashchandrab]

This is not actually fixing the issue. If you notice the helm chart values file at digit-upstream/DIGIT-DevOps/deploy-as-code/charts/urban/birth-death-services/values.yaml, the environment variable SCHEMA_NAME is getting passed conditionally as shown below

# Init Containers Configs
initContainers:
  dbMigration:
    enabled: true
    schemaTable: "birth_death_services_schema"
    image:
      repository: "birth-death-services-db"
      tag: "v1.1.0-6158d90905-14"
    env: |
        {{- if index .Values "bnd-ismultischema-enabled" }}        
        - name: SCHEMA_NAME
          value: {{ index .Values "bnd-schemas" | quote }}
        {{- end }}

if we don't pass the variables bnd-ismultischema-enabled, the given fix is not solving the issue. For now, I passed the variable by manually editing the deployment and its resolved. Just wanted to understand whether any other generic fix can be applied to pass the SCHEMA_NAME as public. The same behavior is noticed other services like billing-service and hrms etc.. . Do we need to update the values.yaml of the charts where we have the above logic or is there any better way to handle this.

[DIGIT-support]

@JithendarKumar-eGov can you please look into this? Thanks!