Skip to main content

volumes

Creates, updates, deletes, gets or lists a volumes resource.

Overview

Namevolumes
TypeResource
Iddigitalocean.block_storage.volumes

Fields

NameDatatypeDescription
column_anon``

Methods

NameAccessible byRequired ParamsDescription
volumes_getSELECTvolume_idTo show information about a block storage volume, send a GET request to /v2/volumes/$VOLUME_ID.
volumes_listSELECTTo list all of the block storage volumes available on your account, send a GET request to /v2/volumes. ## Filtering Results ### By Region The region may be provided as query parameter in order to restrict results to volumes available in a specific region. For example: /v2/volumes?region=nyc1 ### By Name It is also possible to list volumes on your account that match a specified name. To do so, send a GET request with the volume's name as a query parameter to /v2/volumes?name=$VOLUME_NAME. Note: You can only create one volume per region with the same name. ### By Name and Region It is also possible to retrieve information about a block storage volume by name. To do so, send a GET request with the volume's name and the region slug for the region it is located in as query parameters to /v2/volumes?name=$VOLUME_NAME&region=nyc1.
volumes_createINSERTTo create a new volume, send a POST request to /v2/volumes. Optionally, a filesystem_type attribute may be provided in order to automatically format the volume's filesystem. Pre-formatted volumes are automatically mounted when attached to Ubuntu, Debian, Fedora, Fedora Atomic, and CentOS Droplets created on or after April 26, 2018. Attaching pre-formatted volumes to Droplets without support for auto-mounting is not recommended.
volumes_deleteDELETEvolume_idTo delete a block storage volume, destroying all data and removing it from your account, send a DELETE request to /v2/volumes/$VOLUME_ID. No response body will be sent back, but the response code will indicate success. Specifically, the response code will be a 204, which means that the action was successful with no returned body data.
volumes_delete_by_nameDELETEBlock storage volumes may also be deleted by name by sending a DELETE request with the volume's name and the region slug for the region it is located in as query parameters to /v2/volumes?name=$VOLUME_NAME&region=nyc1. No response body will be sent back, but the response code will indicate success. Specifically, the response code will be a 204, which means that the action was successful with no returned body data.

SELECT examples

To list all of the block storage volumes available on your account, send a GET request to /v2/volumes. ## Filtering Results ### By Region The region may be provided as query parameter in order to restrict results to volumes available in a specific region. For example: /v2/volumes?region=nyc1 ### By Name It is also possible to list volumes on your account that match a specified name. To do so, send a GET request with the volume's name as a query parameter to /v2/volumes?name=$VOLUME_NAME. Note: You can only create one volume per region with the same name. ### By Name and Region It is also possible to retrieve information about a block storage volume by name. To do so, send a GET request with the volume's name and the region slug for the region it is located in as query parameters to /v2/volumes?name=$VOLUME_NAME&region=nyc1.

SELECT
column_anon
FROM digitalocean.block_storage.volumes
;

INSERT example

Use the following StackQL query and manifest file to create a new volumes resource.

/*+ create */
INSERT INTO digitalocean.block_storage.volumes (
data__name,
data__description,
data__size_gigabytes,
data__tags,
data__snapshot_id,
data__filesystem_type,
data__region,
data__filesystem_label
)
SELECT
'{{ name }}',
'{{ description }}',
'{{ size_gigabytes }}',
'{{ tags }}',
'{{ snapshot_id }}',
'{{ filesystem_type }}',
'{{ region }}',
'{{ filesystem_label }}'
;

DELETE example

Deletes the specified volumes resource.

/*+ delete */
DELETE FROM digitalocean.block_storage.volumes
WHERE = '{{ }}';