mirror of https://github.com/datahub-project/datahub.git synced 2025-07-24 18:10:11 +00:00

History

build: use versioning in gradle consistent with ci (#13259 )

Enable use of gradle for all image builds for publishing, eliminating the per-image build action in docker-unified.yml that duplicated what was in gradle but used slightly different mechanisms to determine what is the tag. Enabled gradle build to consume tags provided by the workflow and produce tags same as earlier.

Use bake matrix builds to build slim/full versions of datahub-ingestion, datahub-actions.

Publish images and scan relies on gradle to get the list of images, via depot.

Image publish and scans run once a day on schedule or on manual triggers only.
Pending work: Separate the publish and scans into a separate workflow that runs on a schedule and could also run other tests.

2025-04-24 23:00:03 +05:30

env

fix(opentelemetry): Resolve type mismatch in metrics exporter (#13053 )

2025-04-04 15:51:10 +01:00

Dockerfile

build: use versioning in gradle consistent with ci (#13259 )

2025-04-24 23:00:03 +05:30

README.md

ci(graphql,workflows): Format .md, .graphql, and workflow .yml files via prettier (#13220 )

2025-04-16 16:55:51 -07:00

start.sh

refactor(GMS): migrate GMS to Spring boot (#12389 )

2025-01-23 10:45:40 -06:00

README.md

DataHub Generalized Metadata Store (GMS) Docker Image

Refer to DataHub GMS Service to have a quick understanding of the architecture and responsibility of this service for the DataHub.

Other Database Platforms

While GMS defaults to using MySQL as its storage backend, it is possible to switch to any of the database platforms supported by Ebean.

For example, you can run the following command to start a GMS that connects to a PostgreSQL backend.

(cd docker/ && docker-compose -f docker-compose.yml -f docker-compose.postgre.yml -p datahub up)

or a MariaDB backend

(cd docker/ && docker-compose -f docker-compose.yml -f docker-compose.mariadb.yml -p datahub up)