Add "origin" information to generated pipeline PY/DSL

• Create a basic pipeline (any pipeline will do)
• Run the pipeline
• Open the pipeline in Kubeflow Pipelines Note that version source and description are currently empty.

For the sake of traceability Elyra should (if possible) provide this information to enable Kubeflow Pipelines users to identify the pipeline origin. e.g Elyra <pipeline name>

[ptitzler]

I do believe having identifying information embedded is important for production-ish use cases and would therefore advocate for a staged approach

Motivation: in a managed production environment many pipelines might be running over time. If there’s a need for an ops person to reach out to the owner of a workflow (e.g. because it was/is be utilizing a large amount of resources in a cluster) it should be possible to access identifying pipeline information that associates a pipeline with the entity that submitted it.

[ptitzler]

Is ‘Description’ something you see coming from the end-user (which would likely be helpful)? If not, we could embed what I thought would be good for ‘Version source’ in the description, something like: ‘Elyra 1.0.3 pipeline’. But I think, assuming we can set ‘Description’, this particular value should come from the user and let ‘Version source’ be a “system-owned” value (meaning it derives from and is set by the server).

I haven’t been able to find any information about the version source. I did reach out to a few folks in Slack who might be able to point us in the right direction and am waiting for them to respond. I believe your proposal is good:

• description = user provided (with a useful default if nothing is specified)
• version source = Elyra provided (if possible; if not “version source” information could be the default for ^^)

I do believe having identifying information embedded is important for production-ish use cases and would therefore advocate for a staged approach:

• Stage 1 (quick delivery): description = Elyra generated “static” text (doesn’t require any UI updates or changes to the pipeline metadata)
• Stage 2: <something more comprehensive>