Introduce jmp pkg subcommand for plugin discovery.

[kirkbrauer]

This PR introduces a new subcommand jmp pkg for discovering (and eventually managing) all types of plugin packages for Jumpstarter.

Currently, the following commands are supported:

• jmp pkg list - Lists all locally-installed Jumpstarter plugin packages.
• jmp pkg show <PACKAGE> - Show Jumpstarter-specific details about a plugin package.

Package detection is currently achieved through the pyproject.toml entry-points field. Discovery is supported for drivers, driver clients, and adapters. Package authors must specify at least one valid entry point for the package to be discovered.

The additional --inspect flag allows for deeper inspection by using importlib and inspect to get additional metadata about the detected entry points. This option is not enabled by default as it may be slow for large package lists and potentially unsafe because it calls the driver's client() method to identify the client type name.

The following additional information can be inspected:

• Driver client type name.
• Docstrings for drivers, driver clients, and adapters.
• Check if a driver client has a registered CLI.

Future ideas for expansion of jmp pkg:

• jmp pkg bake --exporter <EXPORTER> - Create a Containerfile or image based on the packages for an exporter/client.
• jmp pkg install <PACKAGE> - Attempt to install a package from a custom registry to PyPi.
• jmp pkg init <NAME> - Template a new driver package.

Depends on #386

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[netlify]

✅ Deploy Preview for jumpstarter-docs ready!

Name	Link
🔨 Latest commit	1e15461
🔍 Latest deploy log	https://app.netlify.com/sites/jumpstarter-docs/deploys/67e6a5ea4d623a00082b6102
😎 Deploy Preview	https://deploy-preview-382--jumpstarter-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[kirkbrauer]

I think this is failing because of re-ordering of keys in JSON, should we sort alphabetically? @NickCao @mangelajo

[NickCao]

I think this is failing because of re-ordering of keys in JSON, should we sort alphabetically? @NickCao @mangelajo

Sort what?

[kirkbrauer]

@NickCao sorting JSON/YAML key names alphabetically to maintain consistency.

[NickCao]

@NickCao sorting JSON/YAML key names alphabetically to maintain consistency.

This can sometimes create ugly outputs, but since python dicts are already unordered, we couldn't do better either.