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

Remove logic setting resolvers feature flag in e2e tests #6786

Merged
merged 1 commit into from
Jun 13, 2023

Conversation

lbernick
Copy link
Member

@lbernick lbernick commented Jun 7, 2023

Resolution is a beta feature, and resolvers are now enabled by default.
Therefore, there is no logic needed to patch the resolvers configmap when "enable-api-fields" is set to "stable".
In addition, we don't gate installation of resolvers on the "enable-api-fields" feature flag,
and doing so in tests isn't representative of how users install resolvers.

This commit removes logic patching the resolvers configmap.

/kind cleanup

Submitter Checklist

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

  • n/a 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
  • n/a 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.
  • n/a Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

@tekton-robot tekton-robot added kind/bug Categorizes issue or PR as related to a bug. release-note-none Denotes a PR that doesnt merit a release note. labels Jun 7, 2023
@tekton-robot tekton-robot requested review from jerop and wlynch June 7, 2023 15:55
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 7, 2023
@JeromeJu
Copy link
Member

JeromeJu commented Jun 7, 2023

/assign

@lbernick lbernick changed the title Enable resolvers in beta integration tests Remove logic setting resolvers feature flag in e2e tests Jun 7, 2023
@lbernick lbernick closed this Jun 7, 2023
@lbernick lbernick reopened this Jun 7, 2023
@lbernick
Copy link
Member Author

lbernick commented Jun 7, 2023

/hold
something weird is going on with this branch not reflecting my force-push-- need to fix

@tekton-robot tekton-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 7, 2023
Resolution is a beta feature, and resolvers are now enabled by default.
Therefore, there is no logic needed to patch the resolvers configmap when "enable-api-fields" is set to "stable".
In addition, we don't gate installation of resolvers on the "enable-api-fields" feature flag,
and doing so in tests isn't representative of how users install resolvers.

This commit removes logic patching the resolvers configmap.
@lbernick lbernick force-pushed the resolver-beta branch 3 times, most recently from 2e280ff to 437c5a2 Compare June 7, 2023 16:58
@lbernick lbernick added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/bug Categorizes issue or PR as related to a bug. labels Jun 7, 2023
@lbernick lbernick force-pushed the resolver-beta branch 2 times, most recently from 2e280ff to deca6a2 Compare June 7, 2023 17:43
@JeromeJu
Copy link
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 12, 2023
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom, JeromeJu

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 12, 2023
@lbernick
Copy link
Member Author

/retest

@lbernick
Copy link
Member Author

beta tests: #4169
normal integration tests seem to be having issues pulling images.
/retest

@tekton-robot tekton-robot merged commit 5efa357 into tektoncd:main Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants