content library: storage backing
The
storage_backing
structure defines a storage location where content in a library will be stored. The storage location can either be a Datastore or Other type.Representation:
{
"datastore_id": "obj-103",
"storage_uri": "http://myurl.com",
"type": "DATASTORE"
}
"datastore_id": "obj-103",
"storage_uri": "http://myurl.com",
"type": "DATASTORE"
}
Attributes:
Name | Type | Description |
---|---|---|
Optional | ||
type | string | Type (DATASTORE , OTHER ) of content.library.storage_backing. Specifies the type of the content.library.storage_backing. Value is one of:DATASTORE: The content of the library will be stored on a datastore. These are vCenter Server managed datastores, and are logical containers that hide specifics of each storage device. Depending on the type of storage you use, datastores can be backed by the following file system formats:
OTHER: The content of the library will be stored on a remote file system. Supports the following remote file systems:
create operation. It will always be present in the result of the get or list operations. It is not used for the update operation. |
datastore_id | string | Identifier of the datastore used to store the content in the library. Optional. It is only relevant when type has value DATASTORE. This field is optional and it is only relevant when the value of type is DATASTORE.When clients pass a value of this structure as a parameter, the field must be an identifier for the resource type: Datastore . When operations return a value of this structure as a result, the field will be an identifier for the resource type: Datastore . |
storage_uri | URI | URI identifying the location used to store the content in the library. The following URI formats are supported: vSphere 6.5
vSphere 6.0 Update 1
vSphere 6.0
type is OTHER. |