You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pipeline end users, Tekton Pipeline and Task authors might not have the access to the ConfigMap or the controller logs. While we have behavioural flags and the to-be-implemented per feature flags, this might not be easy for users to tell what features are enabled. This issue is to start the discussion of such feature.
Use case
As a Tekton Pipeline author, when trying to debug my failed PipelineRun, I want to explicitly see what features are enabled in Tekton Pipeline for my PipelineRun from its output since I do not have the access to the cluster ConfigMap or controller logs.
I think chains already capture these type of information, but it might make even more sense to have it attached to the PipelineRun/TaskRun objects most likely, as it would removed the need for chains (or any other components in need of this information) to figure it on its own or re-invent the wheel.
So I am 👍🏼 on this. We need to figure out what form it would take 👼🏼 .
Feature request
Pipeline end users, Tekton Pipeline and Task authors might not have the access to the ConfigMap or the controller logs. While we have behavioural flags and the to-be-implemented per feature flags, this might not be easy for users to tell what features are enabled. This issue is to start the discussion of such feature.
Use case
As a Tekton Pipeline author, when trying to debug my failed PipelineRun, I want to explicitly see what features are enabled in Tekton Pipeline for my PipelineRun from its output since I do not have the access to the cluster ConfigMap or controller logs.
related: tektoncd/community#1034
The text was updated successfully, but these errors were encountered: