State specific service changes

Note: - Kafka and DB is commonly shared by all services in central-Instance

1. If the service is posting any messages to Kafka, then it is advised that Kafka topic appends the schema(namespace) name to the Kafka topic by default in the config. Else make the topics unique so that it doesn’t bring confusion with the topics used by services similar to this one from other environments.

2. If the service has persister configs then the topics in the config should be updated by appending the schema name to the Kafka topic in the persister config.
   if the producer is producing a unique topic then the same should be followed here instead of the convention mentioned above.
   pt-calculator is a state-specific service.

   Open

   

    

3. Any host reference to the multi-schema service running in the digit namespace should be referred with digit namespace or the host be changed to internal-gateway if not sure of the namespace in which the service is running.

   a. if the current state-specific service is running in a namespace called statea, then the reference to a multischema service called property-service should be to http://property-service:8080.digit/ in the Environment YAML of the given namespace.
   statea.yaml in environments of the helm config.

   property-services: "http://property-services.digit:8080/"

   
   b. else the property host should refer to internal gateway.

   - name: PROPERTY_SERVICE_HOST valueFrom: configMapKeyRef: name: egov-service-host key: internal-gateway

    

4. {Add more}