Gets an item from the ApiSdk.v2.volumes.item.actions.item collection
A unique numeric ID that can be used to identify and reference an action.
To retrieve all actions that have been executed on a volume, send a GET request to /v2/volumes/$VOLUME_ID/actions.
OptionalrequestConfiguration: RequestConfiguration<ActionsRequestBuilderGetQueryParameters>Configuration for the request such as headers, query parameters, and middleware options.
To initiate an action on a block storage volume by Id, send a POST request to~/v2/volumes/$VOLUME_ID/actions. The body should contain the appropriateattributes for the respective action.## Attach a Block Storage Volume to a Droplet| Attribute | Details || ---------- | ------------------------------------------------------------------- || type | This must be attach || droplet_id | Set to the Droplet's ID || region | Set to the slug representing the region where the volume is located |Each volume may only be attached to a single Droplet. However, up to fifteenvolumes may be attached to a Droplet at a time. Pre-formatted volumes will beautomatically mounted to Ubuntu, Debian, Fedora, Fedora Atomic, and CentOSDroplets created on or after April 26, 2018 when attached. On older Droplets,additional configurationis required.## Remove a Block Storage Volume from a Droplet| Attribute | Details || ---------- | ------------------------------------------------------------------- || type | This must be detach || droplet_id | Set to the Droplet's ID || region | Set to the slug representing the region where the volume is located |## Resize a Volume| Attribute | Details || -------------- | ------------------------------------------------------------------- || type | This must be resize || size_gigabytes | The new size of the block storage volume in GiB (1024^3) || region | Set to the slug representing the region where the volume is located |Volumes may only be resized upwards. The maximum size for a volume is 16TiB.
The request body
OptionalrequestConfiguration: RequestConfiguration<ActionsRequestBuilderPostQueryParameters>Configuration for the request such as headers, query parameters, and middleware options.
To retrieve all actions that have been executed on a volume, send a GET request to /v2/volumes/$VOLUME_ID/actions.
OptionalrequestConfiguration: RequestConfiguration<ActionsRequestBuilderGetQueryParameters>Configuration for the request such as headers, query parameters, and middleware options.
To initiate an action on a block storage volume by Id, send a POST request to~/v2/volumes/$VOLUME_ID/actions. The body should contain the appropriateattributes for the respective action.## Attach a Block Storage Volume to a Droplet| Attribute | Details || ---------- | ------------------------------------------------------------------- || type | This must be attach || droplet_id | Set to the Droplet's ID || region | Set to the slug representing the region where the volume is located |Each volume may only be attached to a single Droplet. However, up to fifteenvolumes may be attached to a Droplet at a time. Pre-formatted volumes will beautomatically mounted to Ubuntu, Debian, Fedora, Fedora Atomic, and CentOSDroplets created on or after April 26, 2018 when attached. On older Droplets,additional configurationis required.## Remove a Block Storage Volume from a Droplet| Attribute | Details || ---------- | ------------------------------------------------------------------- || type | This must be detach || droplet_id | Set to the Droplet's ID || region | Set to the slug representing the region where the volume is located |## Resize a Volume| Attribute | Details || -------------- | ------------------------------------------------------------------- || type | This must be resize || size_gigabytes | The new size of the block storage volume in GiB (1024^3) || region | Set to the slug representing the region where the volume is located |Volumes may only be resized upwards. The maximum size for a volume is 16TiB.
The request body
OptionalrequestConfiguration: RequestConfiguration<ActionsRequestBuilderPostQueryParameters>Configuration for the request such as headers, query parameters, and middleware options.
Builds and executes requests for operations under /v2/volumes/{volume_id}/actions