Skip to content

Conversation

@JannikSt
Copy link
Member

@JannikSt JannikSt commented Jan 16, 2026

Summary

  • New prime ssh-keys list to display SSH keys with IDs
  • New prime ssh-keys create for adding keys from file or string
  • New prime ssh-keys delete and set-primary commands
  • Added --ssh-key-id option to prime pods create

Users can now manage SSH keys entirely via CLI.


Note

Introduces SSH key management in the CLI and enables selecting an SSH key during pod creation.

  • New SSHKeysClient with models (SSHKey, SSHKeyList, SSHKeyCreateRequest) to list, create, delete, and set_primary SSH keys (prime_cli/api/ssh_keys.py)
  • New prime ssh-keys command group: list (table/json), create (from file or string), delete, set-primary (prime_cli/commands/ssh_keys.py), and wired into the main CLI (main.py)
  • prime pods create adds --ssh-key-id and includes sshKeyId in the pod request payload (commands/pods.py)

Written by Cursor Bugbot for commit e0e29b2. This will update automatically on new commits. Configure here.

- Add `prime ssh-keys list` command to list SSH keys with IDs
- Add `prime ssh-keys create` command to create new SSH keys
- Add `prime ssh-keys delete` command to delete SSH keys
- Add `prime ssh-keys set-primary` command to set primary key
- Add `--ssh-key-id` option to `prime pods create`

Users can now get SSH key IDs via CLI and use them when creating pods.
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.


if not key_content:
console.print("[red]Error: Must provide either --public-key or --file[/red]")
raise typer.Exit(1)
Copy link

Choose a reason for hiding this comment

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

File overrides valid public key when empty

Low Severity

When both --public-key and --file arguments are provided to ssh-keys create, the file content unconditionally overwrites the key_content variable even if the file is empty. If the user provides a valid --public-key value but also specifies a --file that happens to be empty, their valid public key is silently discarded. The subsequent error message "Must provide either --public-key or --file" is misleading since the user did provide a valid --public-key.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants