vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Currently, json is the only supported format.





 Required fields for -r --record-content 

The required field in JSON data is type.

Resource record type. Valid values: A, AAAA, CNAME, PTR, TXT, MX, SRV.



* For type A, AAAA: Extra required fields are name, rdata.



* name: Resource record name.
* rdata: Content of the resource record.



* ip: IPv4/IPv6 address





* Extra optional fields are ttl.



* ttl: Time to live in seconds. Default value is 900. Valid values: 60, 120, 300, 600, 900, 1800, 3600, 7200, 18000, 43200.





Sample JSON data:

{
     "name": "testA",
     "type": "A",
     "rdata": {
         "ip": "1.2.3.4"
}
}

{
    "name": "testAAAA",
    "type": "AAAA",
    "rdata": {
        "ip": "2001:0db8:0012:0001:3c5e:7354:0000:5db1"
    }
}



* For type CNAME: Extra required fields are name, rdata.



* name: Resource record name.
* rdata: The content of type-CNAME resource record.



* cname: Canonical name.





* Extra optional fields are ttl.



* ttl: Time to live in second. Default value is 900. Valid values: 60, 120, 300, 600, 900, 1800, 3600, 7200, 18000, 43200.





Sample JSON data:

{
    "name": "testCNAME",
    "type": "CNAME",
    "rdata": {
        "cname": "example.com"
}
}



* For type PTR: Extra required fields are name, rdata.



* name: Resource record name.
Example JSON for uploading in a .tar file later.

{
"name": "<workspace_name>",
"type": [
"<terraform_version>"
],
"location": "<location>",
"description": "<workspace_description>",
"tags": [],
"template_repo": {
"url": "<github_source_repo_url>"
},
"template_data": [
{
"folder": ".",
"type": "<terraform_version>",
"env_values":
{
"VAR1":"<val1>"
},
{
"VAR2":"<val2>"
}
],
"variablestore":
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "string",
"secure": true,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "bool",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "list(string)",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "map(number)",
"secure": false,
"description":"<description>"
},
{
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "any",
"secure": false,
"description":"<description>"
}
]
}
],
}
Show more

Example JSON for uploading in a .tar file later.

{
"name": "<workspace_name>",
"type": [
"<terraform_version>"
],
"location": "<location>",
"resource_group": "<resource_group>",
"description": "<workspace_description>",
"tags": [],
"template_repo": {
"url": "<github_source_repo_url>"
},
"template_data": [
{
"folder": ".",
"type": "<terraform_version>",
"env_values":
{
"VAR1":"<val1>"
},
{
"VAR2":"<val2>"
}
],
"variablestore":
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "string",
"secure": true,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "bool",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "list(string)",
<-- </ul> -->

Sample JSON data:
{
"certificate": "-----BEGIN CERTIFICATE-----n...-----END CERTIFICATE-----n",
"private_key": "-----BEGIN PRIVATE KEY-----n...-----END PRIVATE KEY-----n"
}
-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-upload-authenticated-origin-pull-certificate-option" "> --><-- <section "id="section-upload-authenticated-origin-pull-certificate-examples" "> --> Examples Upload authenticated origin pull certificate on zone level for domain 31984fea73a15b45779fa0df4ef62f9b .
"payload": "Rm91ciBzY29yZSBhbmQgc2V2ZW4geWVhcnMgYWdv..."
}
]
}

The following JSON object shows an example returned value for a root key.

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.key+json",
"collectionTotal": 1
},
"resources": [
{
"type": "application/vnd.ibm.kms.key+json",
"id": "2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"aliases":
"alias-1",
"alias-2"
],
"name": "test-root-key",
"state": 1,
"extractable": false,
"crn": "crn:v1:bluemix:public:hs-crypto:us-south:a/f047b55a3362ac06afad8a3f2f5586ea:30372f20-d9f1-40b3-b486-a709e1932c9c:key:2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"imported": false,
"creationDate": "2020-03-05T16:28:38Z",
"createdBy": "...",
"algorithmType": "AES",
"algorithmMetadata": {
"bitLength": "256",
"mode": "CBC_PAD"
},
"algorithmBitSize": 256,
"algorithmMode": "CBC_PAD",
"lastUpdateDate": "2020-03-05T16:39:25Z",
"keyVersion": {
{
"VAR2":"<val2>"
}
],
"variablestore":
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "string",
"secure": true,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "bool",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "list(string);",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "map(number)",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "tuple(string, list(string), number, bool])",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "any",
"secure": false,
"description":"<description>"
}
]
}
],
}
Show more

Example JSON for uploading in a .tar file later.

{
"name": "<workspace_name>",
"payload": "Rm91ciBzY29yZSBhbmQgc2V2ZW4geWVhcnMgYWdv..."
}
]
}

The following JSON object shows an example returned value for a root key.

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.key+json",
"collectionTotal": 1
},
"resources": [
{
"type": "application/vnd.ibm.kms.key+json",
"id": "2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"aliases":
"alias-1",
"alias-2"
],
"name": "test-root-key",
"state": 1,
"extractable": false,
"crn": "crn:v1:bluemix:public:kms:us-south:a/f047b55a3362ac06afad8a3f2f5586ea:30372f20-d9f1-40b3-b486-a709e1932c9c:key:2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"imported": false,
"creationDate": "2020-03-05T16:28:38Z",
"createdBy": "...",
"algorithmType": "Deprecated",
"algorithmMetadata": {
"bitLength": "256",
"mode": "Deprecated"
},
"algorithmBitSize": 256,
"algorithmMode": "Deprecated",
"lastUpdateDate": "2020-03-05T16:39:25Z",
"keyVersion": {
: If JSON is specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

help | --help | -h
: List options available for the command.







 ibmcloud atracker route update 

Use this command to update a route for an Activity Tracker Event Routing target. Any specified value that is different from when the route was originally created will be updated to the value specified in the command.

ibmcloud atracker route update --route ROUTE [--name ROUTE_NAME] [--force] ( [--target-ids TARGETS] [--locations REGIONS] | [--rules RULES] | [--file RULES_DEFINITION_JSON_FILE] ) [--output FORMAT] [--output FORMAT]



 Command options 

--route ROUTE
: The existing name or ID of the route.

--name ROUTE_NAME
: The updated name to be given to the route (optional).

Do not include any personal identifying information (PII) in any resource names.

--file RULES_DEFINITION_JSON_FILE
: A JSON file containing the definition of the rules for route. The file needs to be formatted as follows:

[
{
"location": "LOCATIONS"],
"target_ids": "TARGET_ID"]
}
]

--rules RULES
: A JSON formatted rule definition enclosed in single quotes. For example:

--rules '[{"locations":"global"],"target_ids":"11111111-1111-1111-1111-111111111111"]},{"locations":"us-south","us-east"],"target_ids":"22222222-2222-2222-2222-222222222222","33333333-3333-3333-3333-333333333333"]}]'

--locations LOCATIONS
: List of locations associated with the route. Specify global to include global events.
"VAR1":"<val1>"
},
{
"VAR2":"<val2>"
}
],
"variablestore":
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "string",
"secure": true,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "bool",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "list(string);",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "map(number)",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "tuple(string, list(string), number, bool])",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "any",
"secure": false,
"description":"<description>"
}
]
}
],
}
Show more

Example JSON for uploading in a .tar file later.

{
}



* For type LOC:



* The required fields in JSON data are name, type, data:



* data:



* lat_degrees: Degrees of latitude.
* lat_minutes: Minutes of latitude
* lat_seconds: Seconds of latitude.
* lat_direction: Latitude direction.
* long_degrees: Degrees of longitude.
* long_minutes: Minutes of longitude.
* long_seconds: Seconds of longitude.
* long_direction: Longitude direction.
* altitude: Altitude of location in meters.
* size: Size of location in meters.
* precision_horz: Horizontal precision of location.
* precision_vert: Vertical precision of location.





* The optional fields is ttl.



Sample JSON data:



{
"name": "testLOC",
"type": "LOC",
"data": {
"lat_degrees": 45,
"lat_minutes": 0,
"lat_seconds": 0,
"lat_direction": "N",
"long_degrees": 45,
"long_minutes": 0,
"long_seconds": 0,
"long_direction": "E",
"altitude": 20,
"size": 0,
"precision_horz": 0,
"precision_vert": 0
}
}
Show more



* For type SRV:



* The required fields in JSON data are type, data:



* data:



* service: A service type, prefixed with an underscore.
* proto: A valid protocol.
* priority: Priority.
* weight: The record weight.
* port: The port of the service.
* target: A valid hostname.





* The optional field is ttl.



Sample JSON data:



{
"type": "SRV",
"data": {
"service": "_ftp",
"proto": "_tcp",
Options



* --json: Format output in JSON.



--------------------







 ibmcloud pi virtual-tape-library-networks 



 List all the attached networks. 

ibmcloud pi virtual-tape-library-networks TAPE_LIBRARY_NAME [--json]



* TAPE_LIBRARY_NAME: The name of the virtual tape library.



Options



* --json: Format output in JSON.



--------------------







 ibmcloud pi virtual-tape-library-hard-reboot 



 Hard restart the operating system of a virtual tape library. 

ibmcloud pi virtual-tape-library-hard-reboot TAPE_LIBRARY_ID



* TAPE_LIBRARY_ID: The unique identifier or name of the virtual tape library.



--------------------







 ibmcloud pi virtual-tape-library-immediate-shutdown 



 Immediately shutdown a virtual tape library 

ibmcloud pi virtual-tape-library-immediate-shutdown TAPE_LIBRARY_ID



* TAPE_LIBRARY_ID: The unique identifier or name of the virtual tape library.



--------------------







 ibmcloud pi virtual-tape-library-reset-state 



 Immediately shutdown a virtual tape library 

ibmcloud pi virtual-tape-library-reset-state TAPE_LIBRARY_ID



* TAPE_LIBRARY_ID: The unique identifier or name of the virtual tape library.



--------------------







 ibmcloud pi virtual-tape-library-soft-reboot 



 Soft restart the operating system of a virtual tape library. 

ibmcloud pi virtual-tape-library-soft-reboot TAPE_LIBRARY_ID



* TAPE_LIBRARY_ID: The unique identifier or name of the virtual tape library.



--------------------
"mode": "file",
"file": {}
},
"url": {
"raw": "https://{{endpoint-region}}cloud-object-storage.appdomain.cloud/{{bucket}}/testimage.jpg",
"protocol": "https",
"host":
"{{endpoint-region}}",
"objectstorage",
"softlayer",
"net"
],
"path":
"{{bucket}}",
"testimage.jpg"
]
},
"description": "Create a new binary (image) file in the bucket"
},
"response": ]
},
{
"name": "Retrieve list of files from bucket",
"event":
{
"listen": "test",
"script": {
"id": "aae11dfd-89e5-464d-a6da-44c05652ccec",
"type": "text/javascript",
"exec":
"pm.test("Request was successful", function() {",
" pm.response.to.be.success; ",
"});",
"",
"pm.test("Response contains expected content", function() {",
" pm.expect(pm.response.text()).to.include("ListBucketResult");",
"});"
]
}
}
],
"request": {
"auth": {
"type": "bearer",
"bearer":
{
"key": "token",
"value": "{{iamtoken}}",
"type": "string"
}
]
},
"method": "GET",
"header": ],
def put_object_add_legal_hold(bucket_name, object_name, file_text, legal_hold_id):
print("Add legal hold {0} to {1} in bucket {2} with a putObject operation.n".format(legal_hold_id, object_name, bucket_name))

cos.put_object(
Bucket=bucket_name,
Key=object_name,
Body=file_text,
RetentionLegalHoldId=legal_hold_id)

print("Legal hold {0} added to object {1} in bucket {2}n".format(legal_hold_id, object_name, bucket_name))

def copy_protected_object(source_bucket_name, source_object_name, destination_bucket_name, new_object_name):
print("Copy protected object {0} from bucket {1} to {2}/{3}.n".format(source_object_name, source_bucket_name, destination_bucket_name, new_object_name))

copy_source = {
"Bucket": source_bucket_name,
"Key": source_object_name
}

cos.copy_object(
Bucket=destination_bucket_name,
Key=new_object_name,
CopySource=copy_source,
RetentionDirective="Copy"
)

print("Protected object copied from {0}/{1} to {2}/{3}n".format(source_bucket_name, source_object_name, destination_bucket_name, new_object_name));

def complete_multipart_upload_with_retention(bucket_name, object_name, upload_id, retention_period):
print("Completing multi-part upload for object {0} in bucket {1}n".format(object_name, bucket_name))

cos.complete_multipart_upload(
Bucket=bucket_name,
Key=object_name,
MultipartUpload={
Accessing Personal Persistent Storage 



  Window Image: 



1.  Reserve Windows image as normal image
2.  After login, click folder icon
3.  Click My PC, then you remote storage will be shown. Please be patient if it is hanging at beginning.







  Linux Image 



1.  Reserve Linux Image as normal
2.  SSH into the virtual machine, NFS folder is onlineFiles, or /home/username/onlineFiles.
Bucket name: masms-XX-X-XXX-XXXXX-"InstanceName"-XX-XXX-cust-files





 Doclink and Attachment Files 

Doclink and Attachment Files should be uploaded to the following IBM Cloud COS bucket. Please upload your doclinks directory with all required subfolders The structure of these files and directories will be maintained when copied to the Manage server location.

Bucket name: masms-XX-X-XXX-XXXXX-"InstanceName"-XX-XXX-cust-files

Note:

The DOCINFO path within the Manage database will need to be updated to /doclinks/"folderStructure"/... It is the customer's responsibility to change all the references. The IBM SRE team prefers customers to carry out this database change and then take the database export so that the database IBM will restore will have this change already.





 Overview Documents 

High-level overviews of the different migration considerations can be found in the attached documents.

Spreadsheet with MAS-SaaS Migration Swimlanes (Roles and Responsibilities):

[MAS-SaaS Spreadsheet with Roles and Responsibilities](https://www.ibm.com/support/pages/system/files/inline-files/Swimlanes-v3_0.xlsx)

Presentation of MS-SaaS Migration Steps:

[MAS-SaaS Presentation of Migration Steps](https://ibm.box.com/shared/static/e2e9i3dir373gdzm8kwdvpzqgfi83uvp.pptx)

MS-SaaS Migration Questionaire:

[MAS-SaaS Migration Questionaire](https://ibm.box.com/shared/static/plkrslw49s5ugr6qnf04g0p1atnujtpr.xls)
Bucket name: masms-XX-X-XXX-XXXXX-"InstanceName"-XX-XXX-cust-files





 Doclink and Attachment Files 

Doclink and Attachment Files should be uploaded to the following IBM Cloud COS bucket. Please upload your doclinks directory with all required subfolders The structure of these files and directories will be maintained when copied to the Manage server location.

Bucket name: masms-XX-X-XXX-XXXXX-"InstanceName"-XX-XXX-cust-files

Note:

The DOCINFO path within the Manage database will need to be updated to /doclinks/"folderStructure"/... It is the customer's responsibility to change all the references. The IBM SRE team prefers customers to carry out this database change and then take the database export so that the database IBM will restore will have this change already.





 Overview Documents 

High-level overviews of the different migration considerations can be found in the attached documents.

Spreadsheet with MAS-Dedicated Migration Swimlanes (Roles and Responsibilities):

[MAS-Dedicated Spreadsheet with Roles and Responsibilities](https://www.ibm.com/support/pages/system/files/inline-files/Swimlanes-v3_0.xlsx)

Presentation of MS-Dedicated Migration Steps:

[MAS-Dedicated Presentation of Migration Steps](https://ibm.box.com/shared/static/e2e9i3dir373gdzm8kwdvpzqgfi83uvp.pptx)

MS-Dedicated Migration Questionaire:

[MAS-Dedicated Migration Questionaire](https://ibm.box.com/shared/static/plkrslw49s5ugr6qnf04g0p1atnujtpr.xls)
"id": "a8363887-2b04-4deb-a75b-10220d30e856",
"type": "text/javascript",
"exec":
"pm.test("Request was successful", function() {",
" pm.response.to.be.success; ",
"});"
]
}
}
],
"request": {
"auth": {
"type": "bearer",
"bearer":
{
"key": "token",
"value": "{{iamtoken}}",
"type": "string"
}
]
},
"method": "DELETE",
"header": ],
"body": {
"mode": "raw",
"raw": ""
},
"url": {
"raw": "https://{{endpoint-region}}cloud-object-storage.appdomain.cloud/{{bucket}}/testimage.jpg",
"protocol": "https",
"host":
"{{endpoint-region}}",
"objectstorage",
"softlayer",
"net"
],
"path":
"{{bucket}}",
"testimage.jpg"
]
},
"description": "Retrieve a binary file from the bucket"
},
"response": ]
},
{
"name": "Delete bucket",
"event":
{
"listen": "test",
"script": {
"id": "3cebb9d7-90ee-42c0-9154-b26bd229e179",
"type": "text/javascript",
"exec":
"url": {
"raw": "https://{{endpoint-region}}cloud-object-storage.appdomain.cloud/{{bucket}}?cors=",
"protocol": "https",
"host":
"{{endpoint-region}}",
"objectstorage",
"softlayer",
"net"
],
"path":
"{{bucket}}"
],
"query":
{
"key": "cors",
"value": ""
}
]
},
"description": "Retrieve the list of files available in the bucket"
},
"response": ]
},
{
"name": "Delete bucket CORS config",
"event":
{
"listen": "test",
"script": {
"id": "83ce0bed-572f-4c16-b45f-67a7a9cc5550",
"type": "text/javascript",
"exec":
"pm.test("Request was successful", function() {",
" pm.response.to.be.success; ",
"});"
]
}
}
],
"request": {
"auth": {
"type": "bearer",
"bearer":
{
"key": "token",
"value": "{{iamtoken}}",
"type": "string"
}
]
},
"method": "DELETE",
"header": ],
"body": {
"mode": "raw",
"raw": ""
},
"url": {
attach](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/pi_volume_attach)<br> * [ibm_pi_volume_group](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/pi_volume_group)<br> * [ibm_pi_volume_group_action](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/pi_volume_group_action)<br> * [ibm_pi_volume_onboarding](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/pi_volume_onboarding)<br> * [ibm_pi_vpn_connection](https://registry.terraform.io/providers/IBM-Cloud/ibm/1.37.0/docs/resources/pi_vpn_connection)<br> * [ibm_pi_vpn_ike_policy](https://registry.terraform.io/providers/IBM-Cloud/ibm/1.37.0/docs/resources/pi_vpn_ike_policy)<br> * [ibm_pi_vpn_ipsec_policy](https://registry.terraform.io/providers/IBM-Cloud/ibm/1.37.0/docs/resources/pi_vpn_ipsec_policy)<br><br><br> <br><br> * [ibm_pi_catalog_images](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/pi_catalog_images)<br> * [ibm_pi_cloud_connection]
Microsoft SharePoint On Prem 

Crawl documents that are stored in a Microsoft SharePoint data source that is hosted on premises.

IBM Cloud

IBM Cloud only

This information applies only to managed deployments. For more information about connecting to an on-premises SharePoint data source from an installed deployment, see [SharePoint On Prem](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-sharepoint-onprem-cp4d).



 What documents are crawled 

During the initial crawl of the content, documents from all of the objects that can be accessed from the site collection path that you specify are crawled and added to your collection. Custom metadata that is associated with the SharePoint content is crawled also. You can crawl one site collection path per collection. You cannot crawl Personal SiteCollections.

During subsequent scheduled recrawls, only new and modified documents are crawled and any changes are reflected in your collection. Documents that are deleted from the external data source are not deleted from the collection.

All Discovery data source connectors are read-only. Regardless of the permissions that are granted to the crawl account, Discovery never writes, updates, or deletes any content in the original data source.

The following table illustrates the objects that Discovery can crawl.



Table 1. Data sources crawling support

 Data source Objects that are crawled 

 Microsoft SharePoint On Prem SiteCollections, Sites, SubSites, Lists, List Items, Document Libraries, List Item Attachments 







 Data source requirements 

In addition to the [data source requirements](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-sourcespublic-requirements) for all managed deployments, your SharePoint On Prem data source must meet the following requirements:



* You can connect to a SharePoint 2013, 2016, or 2019 on-premises data source.
* The user ID must have SiteCollection Administrator permission and be able to access all of the sites and lists that they want to crawl.
* The crawler supports Windows New Technology LAN Manager (NTLM) v1 authentication only. It does not support NTLM v2 or Security Assertion Markup Language (SAML) authentication.
productId: '1000050',
date: '2019-01-25T20:00:00.000Z'
}

const bulkDocs = { docs: [eventDoc1, eventDoc2] };

service.postBulkDocs({
db: 'events',
bulkDocs: bulkDocs
}).then(response => {
console.log(response.result);
});

The previous Go example requires the following import block:

import (
"encoding/json"
"fmt"
"github.com/IBM/cloudant-go-sdk/cloudantv1"
"github.com/IBM/go-sdk-core/v5/core"
)

All Go examples require the service object to be initialized. For more information, see the API documentation's [Authentication section](https://cloud.ibm.com/apidocs/cloudant?code=goauthentication-with-external-configuration) for examples.

See an example JSON structure to request bulk update of documents:

{
"docs": [
{
"name": "Nicholas",
"age": 45,
"gender": "female",
"_id": "96f898f0-f6ff-4a9b-aac4-503992f31b01",
"_attachments": {

},
"_rev": "1-54dd23d6a630d0d75c2c5d4ef894454e"
},
{
"name": "Taylor",
"age": 50,
"gender": "female",
"_id": "5a049246-179f-42ad-87ac-8f080426c17c",
"_attachments": {

},
For stand-alone volumes, the Attachment Type column is blank (-). The Action menu (...) at the end of a table row provides a link for [attaching a Block Storage for VPC volume to an instance](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagesnapshots-vpc-restore-unattached-vol).

You can continue creating more Block Storage for VPC volumes or manage existing volumes.



* [View details about a Block Storage for VPC volume.](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storage)
* [Detach a volume from a virtual server instance.](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storagedetach)
* [Delete a Block Storage for VPC volume.](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storagedelete)