Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output of enabled features for a PipelineRun/TaskRun #7093

Open
JeromeJu opened this issue Sep 6, 2023 · 1 comment
Open

Output of enabled features for a PipelineRun/TaskRun #7093

JeromeJu opened this issue Sep 6, 2023 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@JeromeJu
Copy link
Member

JeromeJu commented Sep 6, 2023

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

@JeromeJu JeromeJu added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 6, 2023
@vdemeester
Copy link
Member

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 👼🏼 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants