Repository navigation
marquez module: MARQUEZ_HOST=${service.host} resolvet niet op het Compose-netwerk #1037
Description
Loose end noted in de body van #1028 (pre-existing, los van #1010).
Het experimentele marquez-module (modules-experimental/observability/marquez/module.yaml) zet MARQUEZ_HOST: ${service.host} = "marquez", maar de compose services heten marquez-api / marquez-web, dus die host resolvet niet op het Compose-netwerk. De lineage-sink contract van marquez valt niet onder de E150-check.
Voorstel: host via het serviceName-mechanisme of een expliciete service-naam adverteren, of het module fixen in modules-experimental.
Activity
RonaldHensbergen commentedon Oct 31, 2026
Resolved by #1047 (merged): the marquez module now sets
MARQUEZ_HOST: ${service.services.marquez-api}, which resolves to the API service's rendered compose DNS name (marquez-api/<id>-marquez-api), and thelineage-sinkcontract is covered by the E150 host cross-check (sink kinds checkhost,connectionUri, andserviceName). Covered by tests/test_marquez_lineage_sink_host.py (asserts MARQUEZ_HOST == "marquez-api"), passing. The remaining ${service.host} use is the containerhostname:field, which is not a network dial.