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

Add plugin to krew #16

Closed
timebertt opened this issue May 22, 2024 · 2 comments · Fixed by #27
Closed

Add plugin to krew #16

timebertt opened this issue May 22, 2024 · 2 comments · Fixed by #27
Assignees
Labels
enhancement New feature or request

Comments

@timebertt
Copy link
Owner

Usually, one would install new kubectl plugins via krew.

The history plugin should be added to krew to make it easy to discover, install, and update.

For adding the plugin to the krew index, see https://krew.sigs.k8s.io/docs/developer-guide/release/new-plugin/
Before, the plugin can be added, a first version must be released.

For setting up automated krew index updates, see https://krew.sigs.k8s.io/docs/developer-guide/release/automating-updates/ / https://github.com/rajatjindal/krew-release-bot
There is also a goreleaser integration for this, but it seems less popular.

@timebertt timebertt added the enhancement New feature or request label May 22, 2024
@timebertt timebertt self-assigned this May 27, 2024
@timebertt
Copy link
Owner Author

Unfortunately, the history plugin name is already taken in the krew index.
It seems like somebody had the same plugin idea while I was keeping my initial work in a private repo for almost a year without finishing it 🙈
kubernetes-sigs/krew-index#3605

@timebertt
Copy link
Owner Author

Let's rename this repository/plugin to kubectl-revisions, which is not taken in the krew index yet.
revisions plays nicely with the subcommands, it is less catchy though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant