tep: PipelineRun displayName#1174
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@say5 are you still interested to work on this TEP ? I can't see any content though, something might be wrong. |
|
@say5: PR needs rebase. DetailsInstructions 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. |
Revises the stub TEP from tektoncd#1174 (@say5) with a complete design: spec.displayName + status.displayName two-field model, $(params.*) and $(context.pipelineRun.*) substitution via existing ApplyReplacements machinery, write-once status semantics (confirmed by @vdemeester in tektoncd/pipeline#10300), webhook validation with configurable length cap, and client impact for Dashboard and CLI. Fixes tektoncd/pipeline#10300

Description
This pull request proposes the ability to define
displayNameforPipelineRun.Based on TEP-0047: Pipeline Task Display Name representing the same idea but for the list of
PipelineRunobjects.Good example of why it would be good to have it: tektoncd/dashboard#3323