[CDF-28553] Add lineageAnnotation support to workflow version tasks - #3208
[CDF-28553] Add lineageAnnotation support to workflow version tasks#3208Magssch wants to merge 1 commit into
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
Description
Adds
lineageAnnotation(sources/targets as CDF resource URIs) to workflow version tasks, in both the YAML class and the request/response resource classes. The field is gated behind the existingdata_productsalpha flag since even though it requires its own feature flag in CDF, it's main purpose is to be used with data products. The YAML validator rejects it when the flag is off, anddump_resourcestrips it from CDF responses so it does not show up in diffs/dumps. Also adds identifiable list diffing onurifor lineage sources/targets, and finally makes thedata_productsflag visible incdf aboutsince the API itself is now publicly documented.Bump
Changelog
Added
lineageAnnotationon workflow version tasks, declaring the data sources and targets of each task. Requires thedata_productsalpha flag.