As the ability to create and run workflows via the API is now a first-class citizen in the design, the ability to reference workflows via a unique name and version rather than ID is useful.
For example, if you have an external integration that references the workflow such as a Catalog item, it would make sense to be able to reference the workflow by unique-name@version rather than 123451234213213@version.
Tekton uses Namespace + Name to determine what to run. Argo Workflows uses Namespace + Generated Name. GitHub Actions uses org/name@version.
As the ability to create and run workflows via the API is now a first-class citizen in the design, the ability to reference workflows via a unique name and version rather than ID is useful.
For example, if you have an external integration that references the workflow such as a Catalog item, it would make sense to be able to reference the workflow by unique-name@version rather than 123451234213213@version.
Tekton uses Namespace + Name to determine what to run. Argo Workflows uses Namespace + Generated Name. GitHub Actions uses org/name@version.