feat(backend): v2 placeholders - unique placeholders

[Bobgy]

To support resolving such placeholders at runtime:

https://kubeflow-pipelines.readthedocs.io/en/sdk-2.0.1/source/dsl.html?h=dsl.parallelfor#kfp.dsl.PIPELINE_JOB_NAME_PLACEHOLDER

[judahrand]

Is this an issue for tracking the implementation of replacements for things such as {{workflow.status}}?

If so:

{{$.pipeline_task_name}} and {{$.pipeline_task_uuid}} don't seem to work on Vertex AI at the moment (not sure about a self hosted KFP). Is this expected? I've also tried various placeholders to try to access the Pipeline job's status/error (eg. {{$.error}}, {{$.status}}, {{$.error.code}}, etc.) and nothing seems to work. How is this templating working and how does it differ from the old Argo templating?

[Bobgy]

Hi, this is for tracking implementation of {{$.pipeline_task_name}} and {{$.pipeline_task_uuid}} like placeholders, but not status.

[Bobgy]

Can you submit a separate issue for your feature request? And make it clearer it's for KFP v2 or Vertex.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

[tarilabs]

same per #10453 (comment)

/reopen

[google-oss-prow]

@tarilabs: Reopened this issue.

In response to this:

same per #10453 (comment)

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.