For the complete documentation index, see llms.txt. This page is also available as Markdown.

Master Data Service

Master / Reference data for PBMS, Registry, Bridge and SPAR

The Master Data Service is the OpenG2P source of master / reference data shared across the platform. It holds and serves the common lookup data that other services depend on — primarily:

  • Geographic data — the location / administrative-area hierarchy used to qualify addresses and target programs.

  • Partner data — the registry of partner organisations (mnemonics, key-manager reference IDs, active status) used for inter-service trust and routing.

It exposes simple read/lookup APIs (Geo and Partner) consumed by PBMS, Registry, Bridge and SPAR, so master data is defined once and reused consistently everywhere.

Repository organisation

Everything for this service lives in a single consolidated repository:

This one repo contains all of the service's parts together — the application code (the FastAPI master-data API), the Docker image build, and the Helm chart used to deploy it. It replaces what were previously three separate repositories (one each for the code, the Docker build, and the Helm chart).

Versions

Helm version
Master Data Docker
Last modified
Comments

15-Jun-2026

  1. Single consolidated repository master-data-service — master-data source, Docker image, and the Helm chart now live in one repo (previously three separate repositories).

  2. Single Helm chart openg2p-master-data under deployments/charts.

  3. Docker image is built from local in-repo source and tagged with the repository ref — on develop the image is tagged develop.

17-Apr-2026

  1. Initial version of the Master Data API — Partners and Geo lookup data.

THIS VERSION HAS BUGS. Use develop.

On the develop branch the chart version is 0.0.0-develop and the Docker image is tagged develop (the image tag always matches the master-data-service repository ref — a branch name or git tag). Tagged releases will carry semantic versions here. The Last modified date of the 0.0.0-develop row should be updated whenever that version changes.

Last updated

Was this helpful?