feat(core): add lineage.enabled to WorkflowSettings and ProjectConfig - #2235
Merged
Conversation
rafal-hawrylak
requested review from
SuchodolskiEdvin
and removed request for
ikholopov-omni and
kolina
July 30, 2026 06:45
SuchodolskiEdvin
requested changes
Jul 31, 2026
rafal-hawrylak
force-pushed
the
feat-lineage-enabled
branch
2 times, most recently
from
July 31, 2026 20:59
2dbd093 to
3aa6b9f
Compare
kolina
requested changes
Aug 2, 2026
SuchodolskiEdvin
approved these changes
Aug 3, 2026
rafal-hawrylak
force-pushed
the
feat-lineage-enabled
branch
from
August 4, 2026 06:08
3aa6b9f to
0d74314
Compare
kolina
requested changes
Aug 4, 2026
Introduces `LineageSettings { bool enabled }` and threads it through
`WorkflowSettings` (yaml opt-in) into `ProjectConfig` (compiled graph)
so downstream Dataform runners can decide whether to emit OpenLineage
events to Knowledge Catalog (datalineage.googleapis.com) after each
action completes.
Config plumbing only — no emission logic is added in this change.
Consumers (Dataform CLI runner, Dataform Backend) read this field in
follow-up work.
rafal-hawrylak
force-pushed
the
feat-lineage-enabled
branch
from
August 4, 2026 22:49
0d74314 to
3493eb1
Compare
kolina
approved these changes
Aug 5, 2026
rafal-hawrylak
added a commit
that referenced
this pull request
Aug 5, 2026
Introduces `LineageSettings { bool enabled }` and threads it through
`WorkflowSettings` (yaml opt-in) into `ProjectConfig` (compiled graph)
so downstream Dataform runners can decide whether to emit OpenLineage
events to Knowledge Catalog (datalineage.googleapis.com) after each
action completes.
Config plumbing only — no emission logic is added in this change.
Consumers (Dataform CLI runner, Dataform Backend) read this field in
follow-up work.
Porting the changes from PR (#2235)
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
3 participants
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.
Introduces
LineageSettings { bool enabled }and threads it throughWorkflowSettings(yaml opt-in) intoProjectConfig(compiled graph) so downstream Dataform runners can decide whether to emit OpenLineage events to Knowledge Catalog (datalineage.googleapis.com) after each action completes.Config plumbing only — no emission logic is added in this change.