Copyright | (c) 2015-2016 Brendan Hay |
---|---|
License | Mozilla Public License, v. 2.0. |
Maintainer | Brendan Hay <brendan.g.hay@gmail.com> |
Stability | auto-generated |
Portability | non-portable (GHC extensions) |
Safe Haskell | None |
Language | Haskell2010 |
Deletes the specified persistent disk. Deleting a disk removes its data permanently and is irreversible. However, deleting a disk does not delete any snapshots previously made from the disk. You must separately delete snapshots.
See: Compute Engine API Reference for compute.disks.delete
.
Synopsis
- type DisksDeleteResource = "compute" :> ("v1" :> ("projects" :> (Capture "project" Text :> ("zones" :> (Capture "zone" Text :> ("disks" :> (Capture "disk" Text :> (QueryParam "requestId" Text :> (QueryParam "alt" AltJSON :> Delete '[JSON] Operation)))))))))
- disksDelete :: Text -> Text -> Text -> DisksDelete
- data DisksDelete
- ddRequestId :: Lens' DisksDelete (Maybe Text)
- ddProject :: Lens' DisksDelete Text
- ddDisk :: Lens' DisksDelete Text
- ddZone :: Lens' DisksDelete Text
REST Resource
type DisksDeleteResource = "compute" :> ("v1" :> ("projects" :> (Capture "project" Text :> ("zones" :> (Capture "zone" Text :> ("disks" :> (Capture "disk" Text :> (QueryParam "requestId" Text :> (QueryParam "alt" AltJSON :> Delete '[JSON] Operation))))))))) Source #
A resource alias for compute.disks.delete
method which the
DisksDelete
request conforms to.
Creating a Request
Creates a value of DisksDelete
with the minimum fields required to make a request.
Use one of the following lenses to modify other fields as desired:
data DisksDelete Source #
Deletes the specified persistent disk. Deleting a disk removes its data permanently and is irreversible. However, deleting a disk does not delete any snapshots previously made from the disk. You must separately delete snapshots.
See: disksDelete
smart constructor.
Instances
Request Lenses
ddRequestId :: Lens' DisksDelete (Maybe Text) Source #
An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).