[TEP-0144] Add feature flag and doc placeholder

[QuanZhang-William]

Changes

Part of #7270. In TEP-0144 we proposed a new enum field to support built-in param input validation.

This commit adds the feature flag enable-param-enum and documentation placeholder for the feature.

/kind feature

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

[WIP] Add `enable-param-enum` feature flag to gate the use of `Param.Enum` API field

[tekton-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/apis/config/feature_flags.go	94.0%	94.1%	0.1

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/apis/config/feature_flags.go	94.0%	94.1%	0.1

[Yongxuanzhang]

this lgtm

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/apis/config/feature_flags.go	94.1%	94.2%	0.1

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/apis/config/feature_flags.go	94.1%	94.2%	0.1

[QuanZhang-William]

Hi @pritidesai @tektoncd/core-maintainers . I saw your comment here around getting reviews from >1 organizations: #7260 (comment)

I totally agree with the point, especially for PR involves major changes/concepts (like introducing a new CRD); and I believe we follow the rule strictly in TEP proposals.

Going forward, I was wondering for smaller implementation PRs like this, do you feel comfortable if reviews are from the same organization to favour productivity, if they have good domain knowledge?

[jerop]

Going forward, I was wondering for smaller implementation PRs like this, do you feel comfortable if reviews are from the same organization to favour productivity, if they have good domain knowledge?

@QuanZhang-William I also had the same thoughts, raised it for discussion at the governance/community meeting today and opened tektoncd/community#1097 for discussion and to clarify the policy, you're welcome to also chime in there

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerop, Yongxuanzhang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Yongxuanzhang,jerop]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jerop]

thank you for breaking down this work @QuanZhang-William 🙏🏾

/lgtm

---

adding this note as suggested in tektoncd/community#1097 (comment):

sought more input here and on slack but haven't received any yet, this is a small and specific change that was discussed in a TEP plus it can be easily changed if needed (alpha)