Remove jmpctl and go release action

[mangelajo]

Summary by CodeRabbit

• Chores
  • Removed the CLI tool and its related commands from the project.
  • Deleted the workflow for automating CLI releases.
  • Simplified the build process by removing CLI-specific targets from the build configuration.

[coderabbitai]

Walkthrough

This change removes the entire CLI tool functionality for managing "jumpstarter" resources. All related Go source files, Makefile targets, and the GitHub Actions workflow for releasing the CLI have been deleted or updated to exclude the CLI. The build and deployment process is now focused solely on the manager binary.

Changes

File(s) / Path(s)	Change Summary
.github/workflows/goreleaser.yaml	Deleted GitHub Actions workflow for automating CLI tool releases using GoReleaser.
Makefile	Removed build rules and targets for the CLI (jmpctl), updated dependencies for other targets.
cmd/jmpctl/main.go	Deleted the main entry point for the jmpctl CLI tool.
internal/cmd/root.go, internal/cmd/client.go,	Deleted all source files implementing the CLI commands, root command, and Kubernetes client logic.
internal/cmd/exporter.go

Poem

The CLI has hopped away,
No more commands to type today.
The Makefile’s lighter, the workflow’s gone,
Only the manager hops along.
With simpler builds and code so neat,
This rabbit finds the change quite sweet!
🐇✨

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

Makefile (1)

151-151: Add help description for the deploy-exporters target
As written, deploy-exporters: lacks a ## comment, so it won’t appear in the output of make help. Consider adding an inline description to improve discoverability.

 .PHONY: deploy-exporters
-deploy-exporters:
+deploy-exporters: ## Prepare and deploy exporters without CLI dependency.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 01086a6 and 10183a9.

📒 Files selected for processing (6)

• .github/workflows/goreleaser.yaml (0 hunks)
• Makefile (2 hunks)
• cmd/jmpctl/main.go (0 hunks)
• internal/cmd/client.go (0 hunks)
• internal/cmd/exporter.go (0 hunks)
• internal/cmd/root.go (0 hunks)

💤 Files with no reviewable changes (5)

• cmd/jmpctl/main.go
• .github/workflows/goreleaser.yaml
• internal/cmd/root.go
• internal/cmd/client.go
• internal/cmd/exporter.go

⏰ Context from checks skipped due to timeout of 90000ms (6)

• GitHub Check: tests
• GitHub Check: e2e-tests-28d6b1cc3b49ab9ae176918ab9709a2e2522c97e
• GitHub Check: e2e-tests (ubuntu-24.04-arm)
• GitHub Check: e2e-tests (ubuntu-24.04)
• GitHub Check: lint-go
• GitHub Check: deploy-kind

🔇 Additional comments (1)

Makefile (1)

29-29: Simplify all target to build only the manager binary
The all target has been updated to depend solely on build, removing the now-defunct bin/jmpctl dependency. This aligns with the PR’s objective to drop the CLI tool.

[jumpstarter-backport-bot]

Successfully created backport PR for release-0.6:

• [Backport release-0.6] Remove jmpctl and go release action #136