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

volumetype functionality #473

Closed
alessandroargentieri opened this issue Oct 1, 2024 · 2 comments · Fixed by #474
Closed

volumetype functionality #473

alessandroargentieri opened this issue Oct 1, 2024 · 2 comments · Fixed by #474

Comments

@alessandroargentieri
Copy link
Member

Some regions are flagged with the custom_storage_class: true:

$ curl -H "Authorization: Bearer `mycivoapikey`" https://api.civo.com/v2/regions | jq
[
  {
    "code": "<regionCode>",
    "name": "<regionName>",
    ...
    "features": {
         ... 
         "custom_storage_class": true
    },
  },

For these regions we would like to add the new command:

civo volumetypes ls

This will wrap a HTTP call returning a JSON array of elements like:

GET /v2/volumetypes
Response:
[
   {
     "name": "ms-xfs-2-replicas"
     "description": "<OPTIONAL>",
     "flags": ["foo", "bar"] // OPTIONAL
   },
   {
      "name": "ms-xfs-3-replicas"
      "description": "<OPTIONAL>",
      "flags": ["foo", "bar"] // OPTIONAL
    },
]

The user can select a volumetype.name and pass to the following:

civo instance create myinstance --volume-type=<VOLUMETYPENAME_HERE>
civo volume create myvolume --volume-type=<VOLUMETYPENAME_HERE>

The civo instance show <INSTANCE_NAME> and the civo volume show <VOLUME_NAME> will show the VolumeType if it comes in the response (optional).

N.B. It needs a new civogo tag @fulviodenza can you provide it?

@fulviodenza
Copy link
Contributor

fulviodenza commented Oct 1, 2024

@alessandroargentieri Sure, I will do as soon as the PR civo/civogo#209 is merged

@fulviodenza
Copy link
Contributor

fulviodenza commented Oct 1, 2024

Here is the tag 0.3.82

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 a pull request may close this issue.

2 participants