ovh / ovh/ovhcloud-cli

[Feature]: Harmonize command names and add retype feature for block storage volumes

Open
#126 0 comments 0 reactions 1 assignee View on GitHub

@martinovh is already working on this.

Since Jan 28, 2026.

Dominant language
Go
Stars
179
Forks
35
Avg merge
2d 10h
Merged PRs (30d)
7

Description

Is there an existing issue for this?
  • I have searched the existing issues
Product concerned

Block Storage

Feature description

The OVHcloud CLI commands for managing block storage volumes have inconsistent naming between Manager/API and lack a retype feature ( edit --type) .

This issue aims to address these points by:

1- Adding the retype command for volumes  : edit <volumeId> --type <newType>
2- Renaming existing commands to harmonize them with the Manager and API
        cloud storage-block create <region> [flags]
        cloud storage-block edit <volume_id>
        cloud storage-block delete <volume_id>
        cloud storage-block upsize <volume_id> <new_size (GB)>
        cloud storage-block list [flags]
        cloud storage-block get <volume_id>
        cloud storage-block attach <volume_id> <instance_id> [flags]
        cloud storage-block detach <volume_id> <instance_id> [flags]
        cloud storage-block snapshot create <volume_id> [flags]
       cloud storage-block snapshot delete <snapshot_id> [flags]
       cloud storage-block snapshot list [flags]
       cloud storage-block backup create <volume_id> <backup_name> [flags]
       cloud storage-block backup delete <backup_id> [flags]
       cloud storage-block create-from-backup <backup_id> <volume_name> [flags]
       cloud storage-block backup restore <backup_id> <volume_id> [flags]
       cloud storage-block backup list [flags]
       cloud storage-block backup get <backup_id> [flags]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.