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

New plugin "kn-plugin-search" for plugin discovery #1604

Open
Tracked by #1583
rhuss opened this issue Feb 9, 2022 · 3 comments
Open
Tracked by #1583

New plugin "kn-plugin-search" for plugin discovery #1604

rhuss opened this issue Feb 9, 2022 · 3 comments
Assignees
Labels
triage/accepted Issues which should be fixed (post-triage)

Comments

@rhuss
Copy link
Contributor

rhuss commented Feb 9, 2022

In order to move forward with allowing users to discover available plugins, it is proposed to create a new plugin kn-plugin-search which introduces a kn plugin search command set queries a list of plugins from a fixed URL (e.g. hosted on the knative.dev website). This should be a YAML file, which contains information about:

  • Plugin name
  • Download location
  • Version information
  • Short description (1 line)
  • Longer Description
  • Usage Example
  • Maybe: Tags

It should be possible to search with name and within the description. Also, an option should be added (e.g. --all for listing all plugins.

The output should by default fit on one line (like in apt-cache search), but a --verbose should enable the full output (including the full description & usage example). Maybe we could decide to show the full output, too, when only a single search result was detected.

This is the first step towards a more complete solution for dynamic discovery from within e.g. a GitHub organization via a naming convention, borrowing some ideas from brew and krew.

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 11, 2022
@dsimansk
Copy link
Contributor

/remove-lifecycle stale

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 11, 2022
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 10, 2022
@rhuss rhuss added triage/accepted Issues which should be fixed (post-triage) and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Development

No branches or pull requests

3 participants