Repository navigation
feat(blueprints): add automated OpenLineage metadata extraction and Marquez governance pipeline - #501
Merged
MartinRst merged 3 commits intoOct 5, 2026
Conversation
…arquez governance pipeline
Member
|
Hello your workflow miss all the extend part otherwise the workflow seems ok! |
…z-data-governance
Contributor
Author
|
Hi @MartinRst, thank you for pointing that out! I have updated the blueprint with the complete Commit: 297a95d. Ready for your review whenever convenient! |
MartinRst
approved these changes
Oct 5, 2026
MartinRst
left a comment
MartinRst
left a comment
Member
There was a problem hiding this comment.
Looks good thanks for the update!
MilosPaunovic
added
the
kind/external
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This pull request adds an enterprise data governance and metadata tracking blueprint to the Kestra blueprints library:
flows/openlineage-marquez-data-governance.yaml.It automates end-to-end data lineage extraction during DuckDB analytical SQL transformations, formatting standard OpenLineage 1-0-0 run event payloads (schema facets, input and output datasets, parent job facets) and emitting them to a Marquez metadata backend with automated quality gating and Slack alerting.
Architectural Highlights
io.kestra.plugin.core.trigger.Schedule: Runs automated nightly compliance sweeps (04:00 UTC).io.kestra.plugin.core.trigger.Webhook: Supports real-time upstream CDC or ingestion pipeline gating viaLINEAGE_WEBHOOK_KEY.io.kestra.plugin.jdbc.duckdb.Queries: Curates raw transaction streams into aggregated customer revenue marts.io.kestra.plugin.scripts.python.Commandsinpython:3.11-slim: Constructs compliant OpenLineage 1-0-0 JSON run events with schema facets, input/output dataset definitions, nominal time, and execution run IDs.io.kestra.plugin.core.http.Request: Dispatches POST payloads to the Marquez lineage ingestion endpoint (/api/v1/lineage).io.kestra.plugin.core.flow.If: Evaluates lineage registration status.then: Dispatches success notifications viaio.kestra.plugin.notifications.slack.SlackIncomingWebhook.else: Emits Slack failure alerts and activates an interactiveio.kestra.plugin.core.flow.Pausegate requiring compliance officer sign-off before downstream pipelines proceed.Track 02 Compliance Checklist
setup_governance_context,run_duckdb_transformation,extract_openlineage_facets,emit_openlineage_to_marquez,verify_marquez_ingestion,notify_slack_success).check_governance_guardrail[If],require_compliance_officer_approval[Pause]).schedule_trigger,webhook_trigger).plugin-jdbc-duckdb,plugin-scripts-python,plugin-notifications).title,shortDescription,metaTitle,metaDescription,description(with all standard sub-headings),tags,subTags,ee: false, anddemo: false.extend.tags: ['Data', 'Infrastructure'](strictly compliant withvalidate-blueprint-tags.yml, <= 3 allowed tags).