-
Notifications
You must be signed in to change notification settings - Fork 232
Fix move enable-api-fields to feature-flags CM #414
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
Fix move enable-api-fields to feature-flags CM #414
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm 👍 /hold for others to review 😄 |
pradeepitm12
left a comment
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.
/lgtm
With PR tektoncd#411 the enable-api-fields for triggers was set in config-defaults-triggers ConfigMap whereas it should be added in feature-flags-triggers ConfigMap so shifting that.
1ee4e8d to
2640153
Compare
| type TriggersProperties struct { | ||
| EnableApiFields string `json:"enable-api-fields,omitempty"` | ||
| // +optional | ||
| OptionalTriggersProperties `json:",inline"` |
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.
👍🏽
|
/lgtm |
Changes
With PR #411 the enable-api-fields for triggers was set in
config-defaults-triggers ConfigMap whereas it should be added in
feature-flags-triggers ConfigMap so shifting that.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Release Notes