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

removes remaining references to 'lookup-plugins-in-path' #481

Merged

Conversation

maximilien
Copy link
Contributor

Removes remaining references to 'lookup-plugins-in-path' which is now renamed to the simpler 'lookup-plugins'

Proposed Changes

  • change references of 'lookup-plugins-in-path' to 'lookup-plugins' (new name for flag)

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Nov 5, 2019
@knative-prow-robot knative-prow-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 5, 2019
@maximilien
Copy link
Contributor Author

/ok-to-test

@knative-prow-robot knative-prow-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Nov 5, 2019
@@ -90,7 +90,7 @@ func TestPluginHandler(t *testing.T) {
})

t.Run("when plugin is in $PATH", func(t *testing.T) {
t.Run("--lookup-plugins-in-path=true", func(t *testing.T) {
t.Run("--lookup-plugins=true", func(t *testing.T) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it that we now have --lookup-plugins and --no-lookup-plugins for boolean params ?

Copy link
Contributor

@rhuss rhuss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From a renaming POV it looks good to me, but shouldn't we switch over to our way to treat boolean values with --lookup-plugins and --no-lookup-plugins ?

As this PR is not harmful I think we can merge it nevertheless.

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 11, 2019
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maximilien, rhuss

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

@knative-prow-robot knative-prow-robot merged commit 1f27eca into knative:master Nov 11, 2019
@maximilien maximilien deleted the cleanup-lookup-plugins-in-path branch December 20, 2019 02:17
coryrc pushed a commit to coryrc/client that referenced this pull request May 14, 2020
coryrc pushed a commit to coryrc/client that referenced this pull request May 14, 2020
* Remove usage of K8S_CLUSTER_OVERRIDE

1. It was removed in knative#481.
1. This is a dupe of a flag in pkg/test/e2e_flags.go, we should have a single approach for such helpers.

* Remove unused import
dsimansk added a commit to dsimansk/client that referenced this pull request Oct 9, 2020
* Update SPEC file for release v0.17.1

* fix(ci): Pin CI setup to 0.17.x versions

* fix(ci): Remove unecessary replace of Eventing imgs
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. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. 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