-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
TEP-0089: Refactor setting of "enforce-nonfalsifiability" feature flag #6527
Conversation
@jerop: GitHub didn't allow me to request PR reviews from the following users: jagathprakash. Note that only tektoncd members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions 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. |
ee38a99
to
b49e78e
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/lgtm |
@jagathprakash: changing LGTM is restricted to collaborators In response to this:
Instructions 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. |
/assign |
/lgtm Thanks @jerop |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/lgtm |
/lgtm |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
In this change, we refactor the code for setting "enforce-nonfalsifiability" feature flag to make it easier to understand, and consistent with the rest of the code. This refactor will make it easier to promote the feature to beta, and beyond. This change also documents that `enable-api-fields` has to be set to `"alpha"` for non-falsifiability to work. This commit also includes a change to `TestNewFeatureFlagsConfigMapErrors` to check the exact error, instead of just checking that there was an error. This is useful in validating that both errors that can be triggered while setting the "enforce-nonfalsifiability" feature flag are tested.
/lgtm |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom 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:
Approvers can indicate their approval by writing |
Changes
In this change, we refactor the code for setting
enforce-nonfalsifiability
feature flag to make it easier to understand, and consistent with the rest of the code. This refactor will make it easier to promote the feature to beta, and beyond.This change also documents that
enable-api-fields
has to be set to"alpha"
for non-falsifiability to work.This commit also includes a change to
TestNewFeatureFlagsConfigMapErrors
to check the exact error, instead of just checking that there was an error. This is useful in validating that both errors that can be triggered while setting theenforce-nonfalsifiability
feature flag are tested./kind cleanup
/cc @jagathprakash
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes