Think of this as a repository which holds all the configuration to configure the the Data Mesh Manager via GitHub Actions for a single domain team or a whole organization.

Teams, their source systems and data products can just be put in their specific folders:

├── dataproducts
│   ├── shelf_warmers.yml
│   └── stock_updated.yml
├── sourcesystems
│   └── stock_service.yml
└── teams
    └── fulfillment.yml

Technically, all example configurations are transformed to json with yq and sent to the Data Mesh Manager with curl.

You can find the GitHub Action configuration here. The API key of the data mesh manager of the corresponding organization has be to set as a repository variable named DMM_API_KEY.

You can find the GitLab CI configuration here. The API key of the data mesh manager of the corresponding organization has be to set as a repository variable named GITOPS_EXAMPLE_API_KEY.