Modify space details
Modifies the space import/update strategies.
Path parameters
| Parameter | Type & Description |
|---|---|
| id required | string The Id of a space which details should be modified. |
Request body
The storage space size in bytes that provider is willing to assign to the space.
storageImport The storage import configuration. Storage import allows to import data from storage to space without need for copying the data.
The storage import configuration. Storage import allows to import data from storage to space without need for copying the data.
The import strategy. One of no_import, simple_scan.
Maximum depth of filesystem tree that will be traversed during storage synchronization.
Flag that enables synchronization of NFSv4 ACLs.
storageUpdate The storage update configuration. Storage update ensures that all changes on storage will be reflected in space.
The storage update configuration. Storage update ensures that all changes on storage will be reflected in space.
The update strategy. One of no_update, simple_scan.
Maximum depth of filesystem tree that will be traversed during storage synchronization.
Period between subsequent scans in seconds (counted from end of one scan till beginning of the following).
Flag determining that synchronized storage will be treated as immutable (only creations and deletions of files on storage will be detected).
Flag determining that deletions of files will be detected.
Flag that enables synchronization of NFSv4 ACLs.
Responses
The space details has been successfully changed.
Invalid request.
error Object describing an error.
Object describing an error.
String identifying the error type. Does not change between error instances.
Human readable error description. May contain information specific to given error instance.
Details about the error instance. The object schema is specific to each error type.
Example
{
"error": {
"id": "badValueString",
"details": {
"key": "name"
},
"description": "Bad value: provided \"name\" must be a string."
}
}Unauthorized request.
Forbidden request.
The user does not exist.
Internal server error.
error Object describing an error.
Object describing an error.
String identifying the error type. Does not change between error instances.
Human readable error description. May contain information specific to given error instance.
Details about the error instance. The object schema is specific to each error type.
Example
{
"error": {
"id": "badValueString",
"details": {
"key": "name"
},
"description": "Bad value: provided \"name\" must be a string."
}
}Services needed to fulfill this request are not running.