vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Collections overview 

This section details how collections should behave. Collections SHOULD have a URL ending in a plural resource name, such as /v2/accounts.



  Response format 

The representation of a collection MUST be an object containing a field with the same plural resource name appearing in the collection's URL. This field MUST contain an array of resources in the collection. This response object MAY also include collection metadata, such as for [pagination](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-pagination).

[1]



  Example collection response 

{
"accounts": [
{
"id": "499aed3c-3f49-4a04-8e69-44c2f2894195",
"company_name": "Aperture Science",
"href": "https://api.example.com/v1/accounts/499aed3c-3f49-4a04-8e69-44c2f2894195"
},
{
"id": "2f27ff7b-3183-4e9a-a085-db457402ee95",
"company_name": "Black Mesa",
"href": "https://api.example.com/v1/accounts/2f27ff7b-3183-4e9a-a085-db457402ee95"
}
]
}







  Individual resource URLs 

Resources belonging to a collection MAY be individually addressable, and if so, their URLs SHOULD start with the URL of the collection.

[2]For example, an account in the /v2/accounts collection would have the URL /v2/accounts/:account_id where :account_id is the unique account identifier.

Each individual resource's URL SHOULD be included in the root of its representation as the href property. This URL SHOULD be complete and begin with the protocol (e.g., https://api.example.com/v2/accounts/499aed3c-3f49-4a04-8e69-44c2f2894195).
[--initial-owner-uid INITIAL_OWNER_UID]
[--user-tags USER_TAGS]
[--mount-targets TARGETS_JSON | @TARGETS_JSON_FILE]
[--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME]
[--output JSON] [-q, --quiet]

This example creates a file share with two mount targets.

ibmcloud is share-create --name my-file-share-8 --zone us-south-1 --profile tier-3iops --size 40 --user-tags env:dev,env:prod --mount-targets '[{"name": "my-target121","vpc": {"name": "vpcl"}},{"name": "my-target122","vpc": {"name": "vpc2"}}]'
Creating file share my-file-share-8 under account vpc1 as user user@mycompany.com...

ID 0e04ca62-e02a-4319-9551-380c7f7cd87f
Name my-file-share-8
CRN crn:[...]
Lifecycle State pending
Zone us-south-1
Profile tier-3iops
Size(GB) 40
IOPS 3000
User Tags env:dev,env:prod
Encryption provider_managed
Mount Targets ID Name VPC ID VPC Name
87171615-f8b4-4ccd-a216-bab12eb1a973 my-target121 81ee2425-7c2f-4042-9d8f-d02b0ee8886c vpc1
b041fc54-f0b9-4397-b68e-2ab032cd1206 my-target122 c338ca08-1256-4420-9932-a9960a0f1cfd vpc2
helm ibmc --update
4. Install the most recent version of the ibm-object-storage-plugin for your operating system.

Example helm ibmc upgrade command for OS X and Linux.

helm ibmc upgrade ibm-object-storage-plugin ibm-helm/ibm-object-storage-plugin --set license=true [--set bucketAccessPolicy=false]

Example helm upgrade command for Windows.

helm upgrade ibm-object-storage-plugin ./ibm-object-storage-plugin --set dcname="${DC_NAME}" --set provider="${CLUSTER_PROVIDER}" --set workerOS="${WORKER_OS}" --region="${REGION} --set platform="${PLATFORM}" --set license=true [--set bucketAccessPolicy=false]

DC_NAME
: The cluster data center. To retrieve the data center, run kubectl get cm cluster-info -n kube-system -o jsonpath="{.data.cluster-config.json}{'n'}". Store the data center value in an environment variable by running SET DC_NAME=<datacenter>. Optional: Set the environment variable in Windows PowerShell by running $env:DC_NAME="<datacenter>".

CLUSTER_PROVIDER
: The infrastructure provider. To retrieve this value, run kubectl get nodes -o jsonpath="{.items[].metadata.labels.ibm-cloud.kubernetes.io/iaas-provider}{'n'}". If the output from the previous step contains softlayer, then set the CLUSTER_PROVIDER to "IBMC". If the output contains gc, ng, or g2, then set the CLUSTER_PROVIDER to "IBMC-VPC". Store the infrastructure provider in an environment variable. For example: SET CLUSTER_PROVIDER="IBMC-VPC".

WORKER_OS and PLATFORM
: The operating system of the worker nodes.
You can use Gateway Appliance or vCenter Server gateway cluster with Juniper vSRX or other device as part of the solution as an option.

The tunnel is established between NSX-T T0 and a customer router routable through Direct Link. If vSRX or other third-party device is used in gateway cluster, you can terminate the tunnel in these devices as well. In this case, NSX-T T0 advertises routes in the vSRX (or other third-party device) through BGP or Static Routes.

For more information about this architecture pattern, see [Architecture pattern for using IPsec over Direct Link with a vCenter Server with NSX-T instance](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-arch-pattern-nsx-t-direct-link-ipsec).





 Private connectivity through transit gateway 

Hybrid cloud connectivity can be established by using [IBM Cloud® Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-about). This solution is applicable for NSX-T based vCenter Server instance, which is provisioned in IBM Cloud classic infrastructure. This pattern requires a [gateway appliance](https://cloud.ibm.com/docs/gateway-appliance?topic=gateway-appliance-aboutfirewall) or [gateway cluster](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-addl-clusters) with Juniper vSRX or other third-party device, which supports GRE. In this solution, GRE tunnel is established between this device and Transit GW Router in a specific Zone. NSX-T T0 advertises routes through vSRX (or other device) to Transit Gateway.
: See the Istio release notes for [Istio 1.4.5](https://istio.io/latest/news/releases/1.4.x/announcing-1.4.5/).
: Resolves the following CVEs



* [CVE-2019-18634](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18634)
* [CVE-2019-3843](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3843)
* [CVE-2016-9840](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9840)
* [CVE-2019-5188](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5188)
* [CVE-2020-1712](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1712)
* [CVE-2018-16888](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16888)
* [CVE-2019-3844](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3844)
* [CVE-2019-20386](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20386)
* [CVE-2016-9843](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9843)
[Knowledge - KB0012739 v0.01](https://watson.service-now.com/nav_to.do?uri=kb_knowledge.do?sys_id=fe1f0beedb8db300d5a971198c96191a) 
 vSphere HA failover in progress Not considered essential for notification. Alarm reviewed as part of proactive daily checks. No additional information 
 Cannot find vSphere HA primary agent Configure to send email one time when unable to find or communicate with HA primary agent. [About vSphere availability](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.avail.doc/GUID-63F459B7-8884-4818-8872-C9753B2E0215.html) 
 vSphere HA host status Configure to send email one time when: vSphere HA agent on a host has an error, vSphere HA detects a network isolated host, vSphere HA detects a network-partitioned host, or vSphere HA detects a host failure. [Troubleshooting vSphere HA host states](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-DF7CEF44-98EC-458A-8614-50CCAEC0A7C5.html) 
 vSphere HA virtual machine failover failed Configure to send email one time when critical for critical appliances. [Creating and using vSphere HA Clusters](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.avail.doc/GUID-5432CA24-14F1-44E3-87FB-61D937831CF6.html)
{parameters} To provision your service instance to use customer-managed encryption, pass the following parameters: '{"kms_info": {"id": <kms_instance_id>, "url": <kms_url>}, "kms_key": {"id": <kms_root_key_id>, "crn": <kms_transaction_crn>}}. 
 {plan_id} The ID of the pricing plan that you want to use. 
 {region} The region in which to provision the service instance. For example, us-south. 
 {resource_group_id} The ID of the resource group in which to provision the service instance. To find the IDs of the available resource groups, run ibmcloud resource groups. 
 {token} A valid IAM bearer token. 



For more information about creating service instances, see [Creating new resource instances by using the API](https://cloud.ibm.com/docs/account?topic=account-manage_resource&interface=api&code=curlcreate-resource-instance-api).





 Creating a Continuous Delivery service instance with Terraform 



1. To install the Terraform CLI and configure the IBM Cloud provider plug-in for Terraform, follow the tutorial for [Getting started with Terraform on IBM Cloud](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started).
2. Create a Terraform configuration file that is named main.tf. In this file, add the configuration to create resource instances by using the HashiCorp Configuration Language. For more information about using this configuration language, see the [Terraform documentation](https://www.terraform.io/docs/language/index.html).

The following example creates a Continuous Delivery service instance by using the ibm_resource_instance resource, where name is a unique, descriptive name that identifies the resource instance.

data "ibm_resource_group" "group" {
name = "default"
}
PostgreSQL The following table lists PostgreSQL supported data types for M_CTR mode in Data Security Broker Manager.



Table 2. CTR Supported Data Types caption-side=

 Original Data Type Encrypted Data Type 

 SMALLINT BYTEA 
 INT, INTEGER BYTEA 
 BIGINT BYTEA 
 REAL, FLOAT4 BYTEA 
 FLOAT8 - Used in Data Security Broker Shield for "double precision" BYTEA 
 DECIMAL, NUMERIC BYTEA 
 VARCHAR - Used in Data Security Broker Shield for "character verification" BYTEA 
 CHAR, CHARACTER, BPCHAR BYTEA 
 TEXT BYTEA 
 JSON, JSONB BYTEA 
 BYTEA BYTEA 
 MONEY BYTEA 
 DATE BYTEA 
 TIMESTAMP - Used in Data Security Broker Shield for "timestamp without time zone" BYTEA 
 TIMESTAMPZ - Used in Data Security Broker Shield for "timestamp with time zone" BYTEA 
 UUID BYTEA 
 BIT BYTEA 
 VARBIT - Used in Data Security Broker Shield for "bit verification" BYTEA
select the HPVS instance for parameter [--instance]:

Select a virtual server:
1. hpnet test1 - crn:v1:staging:public:hpvs:dal10:a/9f63166137084e9d9131e42bfce481a6:3dc2e108-15b3-49db-8664-a7a64235ff97::
2. hpnet test2 - crn:v1:staging:public:hpvs:dal12:a/9f63166137084e9d9131e42bfce481a6:dcf3abcf-4770-4945-9888-96e67eb61b11::
Enter a number>

Enter number 2 to select hpnet test2, you are then prompted to enter a passphrase to encrypt the private key:

ibmcloud hpnet adminkey set --instance hpnet-test2

Generating public/private ed25519 key pair for the admin of hpnet-test2...

Enter passphrase of the private key>
Enter same passphrase again>
OK

Enter a passphrase that you can remember. If you are doing this the first time, the CLI prompts you to authenticate the Hyper Protect Virtual Servers instance, to verify if the server side certification is trusted or not. If the server side certification is trusted, the fingerprint of the server certification is recorded in a local file ($HOME/.hpnet-cfg/known_instances), to avoid repeated authentication requests in subsequently run commands:

Starting to encrypt key '/Users/hexiaohu/.hpnet-cfg/temp/hpnet-test2-71-20-39-e8.priv.tmp'....

Connecting to the server hpnet-test2 [52.117.54.138] ...

Verify the connecting server’s certificate before connecting:
If you're using the CLI or API to assign access, use hpcaas-from-rescale-prod for the service name.

Platform roles

Actions



Table 66. Platform roles - HPCaaS from Rescale
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator null 
 Editor null 
 Operator null 







 Hyper Protect Virtual Server 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use hpvs for the service name.

Platform roles

Service roles

Actions



Table 67. Platform roles - Hyper Protect Virtual Server
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 







 Hyper Protect Crypto Services 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use hs-crypto for the service name.

Platform roles

Service roles

Actions



Table 68. Platform roles - Hyper Protect Crypto Services
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users.
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/a0c07083-f411-446c-9316-7b08d6448c86",
"id": "a0c07083-f411-446c-9316-7b08d6448c86",
"iops": 1000,
"lifecycle_state": "pending",
"name": "my-encrypted-share",
"profile": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/share/profiles/tier-5iops",
"name": "tier-5iops",
"resource_type": "share_profile"
},
"resource_group": {
"crn": "crn:[...]",
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/678523bcbe2b4eada913d32640909956",
"id": "678523bcbe2b4eada913d32640909956",
"name": "Default"
},
"resource_type": "share",
"size": 100,
"mount_targets": [
{
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/a0c07083-f411-446c-9316-7b08d6448c86/mount_targets/ 1b5571cb-536d-48d0-8452-81c05c6f7b80",
"id": "1b5571cb-536d-48d0-8452-81c05c6f7b80",
Licensing 

Select the VMware® components to be ordered with your cluster and specify the licensing option for the components.



 Component bundles for IBM Business Partner users 

If you are an IBM® Business Partner user, you can select a component license bundle when you order a new VMware vSphere® instance. The following bundles are available:



Table 1. IBM Business Partner component bundles for vSphere instances

 Bundle Components 

 Standard with Management vSphere Enterprise Plus, VMware vCenter Server® Standard, VMware Aria Operations™ for Logs, VMware Aria® Operations™ Enterprise 
 Advanced vSphere Enterprise Plus, vCenter Server Standard, VMware Aria Operations for Logs, VMware Cloud Director, NSX® Base 
 Advanced with Networking vSphere Enterprise Plus, vCenter Server Standard, VMware Aria Operations for Logs, NSX Advanced 
 Advanced with Networking and Management vSphere Enterprise Plus, vCenter Server Standard, VMware Aria Operations for Logs, VMware Aria Operations Enterprise, VMware Cloud Director, NSX Enterprise 



You can also include the following VMware® components in your order:



* VMware vSAN™
* VMware Site Recovery Manager
* VMware Aria® Automation™ Enterprise



For IBM Business Partner users, bring your own license (BYOL) is not available.





 Individual components for non-Business Partner users 

If you're a non-Business Partner, you can select the following components for your vSphere instance:



* VMware vSphere Enterprise Plus 7.0u3
* VMware vCenter Server
* VMware NSX - Data Center SP Base, Data Center SP Professional, Data Center SP Advanced, or Data Center SP Enterprise Plus
* VMware vSAN
* VMware Site Recovery Manager
* VMware Aria Automation Enterprise
* VMware Aria Operation Enterprise
* VMware Aria Operations for Logs



Small differences exist between NSX-T Data Center and Data Center SP editions. For more information, see [Product offerings for VMware NSX-T Data Center 3.2.x](https://kb.vmware.com/s/article/86095).





 Licensing options
Initializing service instances using key part files 

Before you can use your Hyper Protect Crypto Services instance, you need to first initialize your service instance by loading the master key. This topic guides you through the steps to initialize your service instance by using key part files through IBM Cloud TKE CLI plug-in.

For an introduction to the approaches of service instance initialization and the related fundamental concepts, see [Initializing service instances](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-introduce-service) and [Introducing service instance initialization approaches](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-instance-mode).

The following diagram gives you an overview of steps you need to take to initialize the service instance using master key parts stored in files. Click each step on the diagram for detailed instructions.

Zoom

![Click each step to get more details on the flow.](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/hs-crypto//images/hsm-initialization-flow.svg)

Figure 1. Task flow of service instance initialization with the TKE CLI plug-in


[Install IBM Cloud CLI](/docs/hs-crypto?topic=hs-crypto-initialize-hsm-prerequisite)

[Log in to IBM Cloud](/docs/hs-crypto?topic=hs-crypto-initialize-hsm-prerequisite)

[Install TKE CLI plug-in](/docs/hs-crypto?topic=hs-crypto-initialize-hsm-prerequisite)

[Set up local directory for key files](/docs/hs-crypto?topic=hs-crypto-initialize-hsm-prerequisite)
(https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unit)[Initialize service instances using key part files You can also initialize your service instance using master key parts that are stored in files on your local workstation. You can use this approach regardless of whether or not your service instance includes recovery crypto units. ](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm)

 Video library 

[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/hs-crypto//images/thumbnail_overview_video.png)<br><br>IBM Cloud Hyper Protect Crypto Services overview](https://mediacenter.ibm.com/media/1_1ipwq52p)[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/hs-crypto//images/thumbnail_initialize_cli.png)<br><br>Initializing Hyper Protect Crypto Services with key parts](https://mediacenter.ibm.com/media/1_9mybz1cr)[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/hs-crypto//images/thumbnail_initialize_smart_card.png)<br><br>Initializing Hyper Protect Crypto Services with smart cards](https://mediacenter.ibm.com/media/1_lo2fmwbb)[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/hs-crypto//images/thumbnail_uko_o365.png)<br><br>Managing compliance of a Microsoft Office 365 environment using Hyper Protect Crypto Services with Unified Key Orchestrator](https://mediacenter.ibm.com/media/1_1pzzhrb8)[![carousel thumbnail](
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"referenced_keystores": [],
"instances": [
{
"id": "ea7b6b27-d71b-4fe9-bbfe-309c7ca713a6",
"label_in_keystore": "IBM CLOUD KEY",
"type": "secret_key",
"keystore": {
"group": "Production",
"type": "ibm_cloud_kms"
}
}
],
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/managed_keys/3dab42dc-6941-4841-8d27-4dabcc5aa09e"
}







 hpcs uko managed-key-activate 

Activate a managed key and perform key installation or activation operations on keystores in the keystore group associated with the managed key.

ibmcloud hpcs uko managed-key-activate --id ID --uko-vault UKO-VAULT --if-match IF-MATCH



* Command options

--id (string)
: Required. The UUID of the key. You can use the ibmcloud hpcs uko managed-keys command to retrieve the key UUID.

--uko-vault (string)
: Required. The UUID of the vault where the update is to take place. You can use the ibmcloud hpcs uko vaults command to retrieve the vault UUID.

--if-match (string)
: Required. The precondition of the update, which is the value of the ETag from the header on a GET request. You can use the ibmcloud hpcs uko managed-key command to retrieve the ETag.
* Example

ibmcloud hpcs uko managed-key-activate
: See the Istio release notes for [Istio 1.4.7](https://istio.io/latest/news/releases/1.4.x/announcing-1.4.7/).
: Resolves the following CVEs



* [CVE-2020-1764](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1764)
* [CVE-2019-19925](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19925)
* [CVE-2019-13750](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13750)
* [CVE-2019-13752](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13752)
* [CVE-2019-19959](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19959)
* [CVE-2019-19926](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19926)
* [CVE-2019-13753](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13753)
* [CVE-2019-13751](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13751)
* [CVE-2019-19923](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19923)
id=self.__gateway_id)
else:
pprint("Can't route thru VLAN %s is not associated" % vlan)
Show more





 Example - Canceling a gateway appliance 

import SoftLayer
from pprint import pprint

def getGatewayMembers(client, appliance_id):
"""
Retrieves the gateway's member(s)
args:
client:
SL client credentials
appliance_id:
ID of the gateway appliance to be reclaimed
returns:
gateway members
"""
mask = 'mask[hardwareId]'
return client['Network_Gateway'].getMembers(id=appliance_id, mask=mask)

def cancelGateway(client, appliance_id):
"""
Cancels a standalone or HA pair gateway
args:
client:
SL client credentials
appliance_id:
ID of the gateway appliance to be reclaimed
returns:
True if all members of the appliance are successfully reclaimed
False otherwise
"""
members = getGatewayMembers(client, appliance_id)

for hardware in members:
billingID = client['Hardware'].getBillingItem(id=hardware['hardwareId'])
result = client['Billing_Item'].cancelItem(False,
False,
"No longer needed",
"", id=billingID['id'])

def main():

client = SoftLayer.create_client_from_env(username=<your_username>,
api_key=<your_api_key>,
endpoint_url="https://api.softlayer.com/xmlrpc/v3")

cancelGateway(client, your_gateway_id)

if __name__ == '__main__':
main()
Show more
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/keystores/f6a5ccc1-7fc3-435e-9637-482e470ba8e8",
"ibm_api_endpoint": "https://us-south.kms.cloud.ibm.com",
"ibm_iam_endpoint": "https://iam.bluemix.net/identity/token",
"ibm_api_key": "",
"ibm_instance_id": "d139ea58-a073-441b-ba4e-dcc8bae58be4",
"ibm_variant": "hpcs",
"ibm_key_ring": "IBM-Cloud-KMS-Internal"
}







 ibmcloud hpcs uko keystore-update 

Update attributes of an internal keystore or an external keystore connection.

ibmcloud hpcs uko keystore-update --id ID --uko-vault UKO-VAULT --if-match IF-MATCH --keystore-body KEYSTORE-BODY



* Command options

--id (string)
: Required. The UUID of the keystore. You can use the ibmcloud hpcs uko keystores command to retrieve the UUID.

--uko-vault (string)
: Required. The UUID of the vault where the update is to take place. You can use the ibmcloud hpcs uko keystores command to retrieve the UUID.

--if-match (string)
: Required. The precondition of the update, which is the value of the ETag from the header on a GET request. You can use the ibmcloud hpcs uko keystore command to retrieve the ETag.