Requirements to enable PGR in a new evironment

To enable PGR Service in any new environment, we would need to perform certain steps.

Configuration Requirements

1. Update the Configs repo with the following requirements:
   Add all mdms configs required

   • Indexer config:
     We will need following indexer files for setting up PGR
     pgr-services.yml
     rainmaker-pgr-indexer.yml

   • Persister config:
     pgr-services-persister.yml

   • Searcher config:
     rainmaker-pgr-v2.yml
     

2. Add all mdms configs required

   • Add all Actions/endpoints required for PGR as mentioned in this file.
     Add all actions with respect to core and business-services as well, like those of - user-service, egov-mdms-service, egov-location, egov-common-masters, egov-idgen, egf-master, otp services, access, egov-workflow-v2, data-uploader, egov-hrms, filestore-service, pdf-service, egov-pdf, report, localization-service, egov-persister, egov-indexer, egov-searcher, dasboard-analytics, dashboard-ingest, digit-ui, pgr.

   • Add Role-Action mapping in roleactions.json file.

   • Add required Roles for the respective PGR service in roles.json.

   • Add DIGIT-UI,RAINMAKER-PGR, Workflow, common-masters, dss-dashboard, egf-master, egov-hrms , tenant folders with their respective files.

   • Also add ULB/city specific data in their respective folders, for instance, create a folder lodhipur and add the respective data files like boundary-data.json required.
     

DevOps Requirements

1. Add all the helm charts with respect to the business-services, core-services and municipal-services. Refer here.

2. Add DevOps level changes in the evironment file. Refer here.
   Add all the paths for files in the configs in the environment file. For instance, add the the path of indexer, persister and searcher files, etc.
   Make sure to add required properties at each service level as defined in the above mentioned environment file.

3. Add all the ui related files.Refer here.

Backend/Frontend Requirements

1. Deploy all required core-services builds to support PGR Service. The core-services include:
   egov-user,egov-workflow-v2,egov-perister,egov-localization,egov-notification-sms,egov-mdms,egov-idgen,egov-url-shortening,egov-hrms

2. Deploy all required business-services builds to support PGR Service. The business-services include:
   dashboard-analytics, dashboard-ingest, egf-master, egov-hrms.

3. Deploy “PGR” municipal service builds.

4. Deploy the Frontend build for PGR.

5. Upsert the required localizations. Refer this document for detailed steps.

6. Upsert the SMS templates as localizations in your environment as well as update them in the SMS portal being used by the state. Refer these sms templates.

7. Add PGR Workflow in your environment.Refer the workflow here.

8. Follow the steps to load data for PGR.Refer here.

9. Refer this document to create user with required roles.