vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud hpcs uko associated-resources-for-target-keystore --id ID --uko-vault UKO-VAULT [--limit LIMIT] [--offset OFFSET] [--sort SORT]



* 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 vaults command to retrieve the vault UUID.

--limit (int64)
: Optional. The number of resources to retrieve. The value must be between 1 and 1000.

--offset (int64)
: Optional. The number of resources to skip. The minimum value is 0.

--sort ([]string)
: Optional. The sorting order. The default value is ["name"]. The list items must match the regular expression /^-?[a-z0-9_.\[\],-]+$/.

--all-pages (bool)
: Optional. Invoke multiple requests to display all pages of the collection for the associated resources for the target keystore.
* Example

ibmcloud hpcs uko associated-resources-for-target-keystore 
--id=93777bca-baef-4070-b9b5-a2e6079df1b4 
--uko-vault=5295ad47-2ce9-43c3-b9e7-e5a9482c362b 
--output json
* Output

The command returns the output similar to the following example:

{
"total_count": 3,
"limit": 20,
"offset": 0,
"first": {
"updated_by": "IBMid-5500093BHN",
"deleted_by": "",
"source_crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/4329073d16d2f3663f74bfa955259139:8d7af921-b136-4078-9666-081bd8470d94::",
"role": "crn:v1:bluemix:public:iam::::serviceRole:Writer",
"name": "my-instance-key-1",
"parameters": {
"role_crn": "crn:v1:bluemix:public:iam::::serviceRole:Writer"
},
"crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/4329073d16d2f3663f74bfa955259139:8d7af921-b136-4078-9666-081bd8470d94:resource-key:23693f48-aaa2-4079-b0c7-334846eff8d0",
"state": "active",
"account_id": "4329073d16d2f3663f74bfa955259139",
"resource_group_id": "0be5ad401ae913d8ff665d92680664ed",
"resource_id": "dff97f5c-bc5e-4455-b470-411c3edbe49c",
"credentials": {
"apikey": "XXXX-YYYY-ZZZZ"",
"endpoints": "https://cos-service-armada-s.us-south.containers.mybluemix.net/endpoints",
Last Operation:
Status create in progress
Message Started create instance operation
Show more
3. To check provisioning status, use the following command:

ibmcloud resource service-instance <INSTANCE_NAME>

When complete, you will see a response like:

Retrieving service instance INSTANCE_NAME in resource group default under account USER's Account as USER...
OK

Name: INSTANCE_NAME
ID: crn:v1:bluemix:public:databases-for-mongodb:us-east:a/40ddc34a953a8c02f109835656860e:dd13152c-fe15-4bb6-af94-fde0af5303f4::
GUID: dd13152c-fe15-4bb6-af94-fde5654765
Location: <LOCATION>
Service Name: databases-for-mongodb
Service Plan Name: standard
Resource Group Name: default
State: active
Type: service_instance
Sub Type: Public
Locked: false
Service Endpoints: public
Created at: 2023-06-26T19:42:07Z
Created by: USER
Updated at: 2023-06-26T19:53:25Z
Last Operation:
Status create succeeded
Message Provisioning mongodb with version 4.4 (100%)
Show more
4. (Optional) Deleting a service instance Delete an instance by running a command like this one:

ibmcloud resource service-instance-delete <INSTANCE_NAME>







 The --parameters parameter 

The service-instance-create command supports a -p flag, which allows JSON-formatted parameters to be passed to the provisioning process. Some parameter values are Cloud Resource Names (CRNs), which uniquely identify a resource in the cloud. All parameter names and values are passed as strings.

For example, if a database is being provisioned from a particular backup and the new database deployment needs a total of 9 GB of memory across three members, then the command to provision 3 GBs per member looks like:
Viewing and deleting VMware Regulated Workloads 

You can view the summary and detailed information of the VMware® Regulated Workloads instances that you provisioned on the Resources > Regulated Workloads page. The available information is similar to that of VMware vCenter Server® instances. For more information, see [Viewing vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_viewinginstances).

If you want to release the components that you ordered in a VMware Regulated Workloads instance, you can delete the instance. The process to delete VMware Regulated Workloads instances is similar to that of vCenter Server instances. For more information, see [Deleting vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletinginstance).



  Related links 



*  [VMware Regulated Workloads overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-overview)
*  [Ordering VMware Regulated Workloads](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-orderinginstance-req)
*  [VMware Regulated Workloads reference architecture overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-archi-overview)
accountIDResourceAttribute, serviceNameResourceAttribute},
}

startConditionAttribute := &iampolicymanagementv1.V2PolicyAttribute{
Key: core.StringPtr("{{environment.attributes.current_time}}"),
Operator: core.StringPtr("dateTimeGreaterThanOrEquals"),
Value: core.StringPtr("2022-12-23T00:00:00+00:00"),
}
endConditionAttribute := &iampolicymanagementv1.V2PolicyAttribute{
Key: core.StringPtr("{{environment.attributes.current_time}}"),
Operator: core.StringPtr("dateTimeLessThanOrEquals"),
Value: core.StringPtr("2022-12-23T23:59:59+00:00"),
}
policyRule := &iampolicymanagementv1.V2PolicyBaseRule{
Operator: core.StringPtr("and"),
Conditions: []iampolicymanagementv1.V2PolicyAttribute{
startConditionAttribute, endConditionAttribute},
}

options := iamPolicyManagementService.NewV2CreatePolicyOptions(
"access",
v2PolicyControl,
)
options.SetSubject(policySubject)
options.SetResource(policyResource)
options.SetRule(policyRule)
options.SetPattern(core.StringPtr("time-based-conditions:once"))

policy, response, err := iamPolicyManagementService.V2CreatePolicy(options)
if err != nil {
panic(err)
}
"algorithmType": "Deprecated",
"algorithmMetadata": {
"bitLength": "256",
"mode": "Deprecated"
},
"algorithmBitSize": 256,
"algorithmMode": "Deprecated",
"lastUpdateDate": "2020-03-05T16:39:25Z",
"keyVersion": {
"id": "436901cb-f4e4-45f4-bd65-91a7f6d13461",
"creationDate": "2020-03-05T16:39:25Z"
},
"dualAuthDelete": {
"enabled": false
},
"deleted": false
}
]
}

The payload or key material for a root key stays within the bounds of a hardware security module and cannot be retrieved.

For a detailed description of the response parameters, see the Key Protect [REST API reference doc](https://cloud.ibm.com/apidocs/key-protect).
c36e9f3a-feaf-4033-8603-687784dc7e51 my-root-key 2020-05-10 17:56:37 +0000 UTC Key does not expire





 Example 5 

Create 20 keys and show them in groups of 5 using the kp keys -n -s options.

 create 20 test keys
$ for I in {1..20}; do
KEY_ID=$(ibmcloud kp key create my-test-key-$I --output json | jq -r '.["id"]')
KEY_NAME=$(ibmcloud kp key show $KEY_ID --output json | jq -r '.["name"]')
echo $KEY_ID $KEY_NAME
done

b70f62a1-4d52-4526-91a9-ce47bf14c2a5 my-test-key-1
215f592c-3e42-47b6-867c-3cc1cce8a8fd my-test-key-2
df530c55-39c0-44e8-b7db-397593f70d90 my-test-key-3
768c9ceb-368b-46f7-9b1d-be211e036fe1 my-test-key-4
f141be88-5a34-4290-8513-4f01d934e75a my-test-key-5
b8794334-eea6-4c0d-8fe1-8086300b13f7 my-test-key-6
87679194-52d0-42af-81e1-bffd64f87315 my-test-key-7
cc7faf46-43cf-43b2-be98-7d1815371639 my-test-key-8
curl -X POST "https://us-south.kms.cloud.ibm.com/api/v2/keys/$KEY_ID/actions/wrap" -H "authorization: Bearer <ACCESS_TOKEN>" -H "bluemix-instance: <KP_INSTANCE_ID>" -H "application/vnd.ibm.kms.key_action+json" -d '{
"plaintext": "q+x3Qi.../BVb8bPj....vVD;",
}'

The response:

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.error+json",
"collectionTotal": 1
},
"resources": [
{
"errorMsg": "Bad Request: Wrap with key could not be performed: Please see reasons for more details (INVALID_FIELD_ERR)",
"reasons":
{
"code": "INVALID_FIELD_ERR",
"message": "The field plaintext must be: a base64 encoded key material: illegal base64 data at input byte 38",
"status": 400,
"moreInfo": "https://cloud.ibm.com/apidocs/key-protect",
"target": {
"type": "field",
"name": "plaintext"
}
}
]
}
]
}

A sample request to unwrap a key that fails:

request:

curl -X POST "https://us-south.kms.cloud.ibm.com/api/v2/keys/$KEY_ID/actions/unwrap" -H "authorization: Bearer <ACCESS_TOKEN>" -H "bluemix-instance: <KP_INSTANCE_ID>" -H "application/vnd.ibm.kms.key_action+json" -d '{
: Name of the API key to be locked, exclusive with UUID.

UUID (required)
: UUID of the API key to be locked, exclusive with NAME.

-f, --force
: Force lock without confirmation.





 Examples 

Lock API key test-api-key:

ibmcloud iam api-key-lock test-api-key

Lock API key with given UUID without confirmation:

ibmcloud iam api-key-lock ApiKey-18f773b0-db53-43f1-ad68-92c667c218fe --force







 ibmcloud iam api-key-unlock 

Unlock a platform API key:

ibmcloud iam api-key-unlock (NAME|UUID) [-f, --force]



 Command options 

NAME (required)
: Name of the API key to be unlocked, exclusive with UUID.

UUID (required)
: UUID of the API key to be unlocked, exclusive with NAME.

-f, --force
: Unlock an API key without confirmation.





 Examples 

Unlock API key test-api-key:

ibmcloud iam api-key-unlock test-api-key

Unlock API key with given UUID without confirmation:

ibmcloud iam api-key-unlock ApiKey-18f773b0-db53-43f1-ad68-92c667c218fe --force







 ibmcloud iam service-api-keys 

List all API keys of a service:

ibmcloud iam service-api-keys ([-a, --all], SERVICE_ID_NAME|SERVICE_ID_UUID) [-f, --force]



 Command options 

-a, --all
: Display all API keys that are associated with all services.

SERVICE_ID_NAME (required)
: Name of the service ID, exclusive with SERVICE_ID_UUID.

SERVICE_ID_UUID (required)
: UUID of the service ID, exclusive with SERVICE_ID_NAME.

-f, --force
To delete a project with the CLI, use the [project delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-delete) command. You can optionally use the -f option to force the delete of a project without confirmation. After a project is soft deleted, you can manage this project with the reclamation commands. The following example soft deletes the myproject project,

ibmcloud ce project delete --name myproject -f

Example output

Deleting project 'myproject'...
OK

To permanently delete a project so that it cannot be restored, specify the --hard option with the [project delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-delete) command. You can optionally use the -f option to force the delete of a project without confirmation. The following example permanently deletes the myproject1 project,

ibmcloud ce project delete --name myproject1 --hard -f

Example output

Deleting project 'myproject1'...
OK

If you specify the --hard option with the [project delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-delete) command, the project is immediately deleted and cannot be restored by using IBM Cloud resource reclamation. If you do not specify the --hard option, the project can be restored within 7 days by using the [reclamation restore](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation-restore) command.

If you previously soft deleted a project (without specifying the --hard option), you can specify a subsequent delete only by using the [project delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-delete) command with the --hard option.
put_data <key> <prop> <value>

Sets prop to value for the entry defined by key.





 get_data 

 <key>: Key of data
 <prop>: Type of property e.g. name, type, tags, signature
 <value>: Value of the property
get_data <key>
get_data <key> <prop>

Prints prop of the entry that is defined by key. If prop is not provided, it returns all of the props for the key. Returns a nonzero exit code when key has no prop.





 save_string (deprecated) 

save_string is deprecated, use set_env instead.

save_string <key> <value>

Saves an arbitrary string that can be retrieved later on with load_string.





 load_string (deprecated) 

load_string is deprecated, use get_env instead.

load_string <key>

Prints the string that is stored in key.
roles <br><br> * <br><br><br> <br><br> * <br><br><br> create, delete, deletecollection, get, list, patch, update, watch 
 secrets <br><br> * <br><br><br> create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 serviceaccounts get, list, watch create, delete, deletecollection, get, list, patch, update, watch, impersonate create, delete, deletecollection, get, list, patch, update, watch, impersonate 
 services get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 services/proxy <br><br> * <br><br><br> create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 statefulsets.apps get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 statefulsets.apps/scale get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 







 IBM Cloud IAM issuer details for RBAC users 

Users with a service access role to IBM Cloud Kubernetes Service in IAM are given [corresponding user roles in RBAC](https://cloud.ibm.com/docs/containers?topic=containers-iam-service-access-rolesrbac_ref). The RBAC user details include a unique issuer ID, subject identifier claim, and Kubernetes username. These details vary with the Kubernetes version of the cluster.
u55"]],"qubit_lo_range":[4.446277685722279,5.446277685722279],4.336091292852979,5.336091292852979],4.553309269904769,5.553309269904769],4.696670530328488,5.696670530328488],4.459101121668277,5.459101121668277],4.617666721552653,5.617666721552653],4.48707252254212,5.48707252254212],4.382464528137721,5.382464528137721],4.518601692764167,5.518601692764167],4.404146072536,5.404146072536],4.448972828741963,5.448972828741963],4.595077933160165,5.595077933160165],4.564263866387169,5.564263866387169],4.613789805679545,5.613789805679545],4.486871939387063,5.486871939387063],4.307744365903194,5.307744365903194],4.382991198196183,5.382991198196183],4.38820378032764,5.38820378032764],4.50976789824746,
-i, --instance-id INSTANCE_ID
[-r, --key-ring KEY_RING_ID]
[-c, --crn-query CRN_PATTERN]
[-k, --key-id KEY_ID_OR_ALIAS]
[-o, --output OUTPUT]



 Examples 

These are examples of kp registrations.

Registration examples show numerous Cloud Resource Names (CRNs). CRNs follow this format:

crn:version:cname:ctype:service-name:location:scope:service-instance:resource-type:resource

See [Cloud Resource Names](https://cloud.ibm.com/docs/account?topic=account-crn) for an in-depth explanation of CRN fields.



 Example 1 

List all registrations, which may include cloud resources such as databases, storage, compute, containers, or messaging.

This example shows the registration between Cloud Object Storage (COS) and Key Protect.

 view all registrations
$ ibmcloud kp registrations --output json

[
{
"keyId": "2cbea94c-6070-4a24-b0f8-7a56e4d7cb6f",
"resourceCrn": "crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:4b636e74-f3ca-40bb-80b8-3bd21801ccb8:bucket:my-cos-kms-bucket",
"createdBy": "crn-crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:4b636e74-f3ca-40bb-80b8-3bd21801ccb8::",
"creationDate": "2020-06-15T16:07:37Z",
ibmcloud tke cryptounit-thrhld-set 
 tke cryptounit-thrhlds Displays signature thresholds for the selected crypto units. ibmcloud tke cryptounit-thrhlds 
 tke cryptounit-zeroize Zeroizes the selected crypto units. ibmcloud tke cryptounit-zeroize 
 tke cryptounits Displays the crypto units for the current resource group. ibmcloud tke cryptounits 
 tke failover-enable Enable or add failover crypto units after you provision a service instance. ibmcloud tke failover-enable 
 tke mk-add Creates and saves a new EP11 master key part. ibmcloud tke mk-add 
 tke mk-rm Removes an EP11 master key part from this workstation. ibmcloud tke mk-rm 
 tke mks Lists EP11 master key parts that are stored on this workstation. ibmcloud tke mks 
 tke sigkey-add Generates and saves a new signature key. ibmcloud tke sigkey-add 
 tke sigkey-rm Removes a signature key from this workstation. ibmcloud tke sigkey-rm 
 tke sigkey-sel Selects the signature keys to use to sign commands. ibmcloud tke sigkey-sel 
 tke sigkeys Lists the signature keys that are stored on this workstation. ibmcloud tke sigkeys 
 tke help, tke h Shows help. ibmcloud tke help 



For more information on each command, run the following command in the TKE CLI plug-in:

ibmcloud tke help <command_name>







 Hyper Protect Crypto Services certificate manager CLI plug-in 

You can use the certificate manager CLI plug-in to manage certificates and administrator signature keys for

[the second layer of authentication in GREP11 or PKCS #11 API connections](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-enable-authentication-ep11).
"lastRotateDate": "2020-06-10T18:13:31Z",
"keyVersion": {
"id": "4330715a-918b-4718-b5ca-9475a214067e",
"creationDate": "2020-06-10T18:13:31Z"
},
"extractable": false,
"state": 1,
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:390086ac-76fa-4094-8cf3-c0829bd69526:key:5b976173-7804-4f82-acfa-bb98098bc528"
}

 unwrap the ciphertext, reveal the original DEK (plaintext),
 and see the new ciphertext (the plaintext wrapped with the rotated root key)
$ ibmcloud kp key unwrap $KEY_ID $CIPHERTEXT --output json

{
"Plaintext": "UPJ4YDwbQMjQG/aqlHsPhHV1CBkpIXngLHFS5+i4UZ4=",
"Rewrapped Plaintext": "eyJjaXBoZXJ0ZXh0IjoiS0FITEFRWjdh ...<redacted>... NWEyMTQwNjdlIn0="
}

 capture the new (rewrapped) plaintext
$ NEWCIPHERTEXT=eyJjaXBoZXJ0ZXh0IjoiS0FITEFRWjdh ...<redacted>... NWEyMTQwNjdlIn0=

 unwrap the ciphertext and reveal the original DEK (plaintext)
$ ibmcloud kp key unwrap $KEY_ID $NEWCIPHERTEXT --output json

{
"crn": "crn:v1:bluemix:public:kms:us-south:a/f047b55a3362ac06afad8a3f2f5586ea:12e8c9c2-a162-472d-b7d6-8b9a86b815a6:key:02fd6835-6001-4482-a892-13bd2085f75d",
"imported": false,
"creationDate": "2020-03-12T03:37:32Z",
"createdBy": "...",
"algorithmType": "Deprecated",
"algorithmMetadata": {
"bitLength": "256",
"mode": "Deprecated"
},
"algorithmBitSize": 256,
"algorithmMode": "Deprecated",
"lastUpdateDate": "2020-03-12T03:37:32Z",
"keyVersion": {
"id": "2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"creationDate": "2020-03-12T03:37:32Z"
},
"dualAuthDelete": {
"enabled": false
},
"deleted": false
}
]
}

For a detailed description of the response parameters, see the Key Protect [REST API reference doc](https://cloud.ibm.com/apidocs/key-protect).





 What's next 



* To find out more about protecting keys with envelope encryption, check out [Wrapping keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-wrap-keys).
* To find out more about programmatically managing your keys, [check out the Key Protect API reference doc](https://cloud.ibm.com/apidocs/key-protect).
:"fc","phase":-0.1410171958813371,"t0":1600},{"ch":"u0","name":"fc","phase":-3.141592653589793,"t0":1600},{"ch":"u13","name":"fc","phase":-3.141592653589793,"t0":0},{"ch":"u13","name":"fc","phase":-1.838344314266873,"t0":1600},{"ch":"u13","name":"fc","phase":-3.141592653589793,"t0":1600},{"ch":"u3","name":"fc","phase":-3.141592653589793,"t0":0},{"ch":"u3","name":"fc","phase":-1.838344314266873,"t0":1600},{"ch":"u3","name":"fc","phase":-3.141592653589793,"t0":1600},{"ch":"u4","name":"fc","phase":-3.141592653589793,"t0":0},{"ch":"u4","name":"fc","phase":-0.1410171958813371,"t0":1600},{"ch":"u4
Also, ensure that the same [plug-ins](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-plugins) are available on Databases for Elasticsearch that you have on the existing Elasticsearch.
* Your our own S3 or IBM Cloud Object Storage repository.



Incremental restores work only if the number of shards of each index on both deployments match. Don't try to reindex and change the number of shards of any indexes once you've taken snapshots.





 Example Migration 

A migration is explored in detail in [Elasticsearch data migration using snapshot and restore](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-esmigration-elasticsearch-snapshot-restore).

In this example, data is still being written while the migration occurs, so multiple snapshots and restores are used.

The example's shell script is available in the [IBM Cloud GitHub repository](https://github.com/IBM/elasticsearch-cos-snapshot-restore). It is provided as a starting point for you to adapt for your use-case.
crn:v1:bluemix:public:kms:us-south:a/3d624cd74a0dea86ed8efe3101341742:90b6a1db-0fe1-4fe9-b91e-962c327df531:key:0bg3e33e-a866-50f2-b715-5cba2bc93234





 Creating a bucket with key-protect enabled 

private static String COS_KP_ALGORITHM = "<algorithm>";
private static String COS_KP_ROOTKEY_CRN = "<root-key-crn>";

public static void createBucketKP(String bucketName) {
System.out.printf("Creating new encrypted bucket: %sn", bucketName);

EncryptionType encType = new EncryptionType();
encType.setKmsEncryptionAlgorithm(COS_KP_ALGORITHM);
encType.setIBMSSEKMSCustomerRootKeyCrn(COS_KP_ROOTKEY_CRN);

CreateBucketRequest req = new CreateBucketRequest(bucketName).withEncryptionType(encType);

_cos.createBucket(req);

System.out.printf("Bucket: %s created!", bucketName);
}
Show more

Key Values



* <algorithm> - The encryption algorithm used for new objects added to the bucket (Default is AES256).
* <root-key-crn> - CRN of the Root Key obtained from the Key Protect service.



SDK References



* Classes



* [CreateBucketRequest](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/model/CreateBucketRequest.html)
* [EncryptionType](https://ibm.github.io/ibm-cos-sdk-java/)



* Methods
CX_d2_u6","samples":-0.00004440674092620611,-0.000004346351488493383],-0.00008985958265839145,-0.000008795091162028257],-0.0001363689370919019,-0.000013347237654670607],-0.00018394473590888083,-0.00001800376412575133],-0.0002325964451301843,-0.00002276559462188743],-0.0002823329996317625,-0.00002763360862445552],-0.0003331628686282784,-0.0000326086301356554],-0.0003850938519462943,-0.000037691424950025976],-0.00043813325464725494,-0.00004288270429242402
"crn": "crn:v1:bluemix:public:is:us-east:a/be636a7a6e4d4b6296bedf669ce8f757::load-balancer:r014-e68a40fb-2b94-4a92-b8bd-dc9bb92c3ef3",
"is_public": false,
"created_at": "2023-02-10T19:36:44Z",
"hostname": "e68a40fb-us-east.lb.appdomain.cloud",
"listeners": [],
"operating_status": "online",
"pools": [],
"private_ips": [
{
"address": "10.241.64.11",
"href": "https://us-east.iaas.cloud.ibm.com/v1/subnets/0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024/reserved_ips/0767-16871e0f-c43a-4b6e-8491-a3e075362046",
"id": "0767-16871e0f-c43a-4b6e-8491-a3e075362046",
"name": "yapping-extract-reawake-bullhorn",
"resource_type": "subnet_reserved_ip"
},
{
"address": "10.241.64.12",
"id": "02fd6835-6001-4482-a892-13bd2085f75d"
},
"rewrappedKeyVersion": {
"id": "12e8c9c2-a162-472d-b7d6-8b9a86b815a6"
}
}

Store and use the new ciphertext value for future envelope encryption operations so that your data is protected by the latest root key.



 Optional Validation 

Verify that the key was successfully rewrapped by base64 decoding the ciphertext value.

$ echo <ciphertext> | base64 --decode

Replace <ciphertext> with the base64 encoded value that was returned in the previous step. The following JSON object shows an example CLI output.

{
"ciphertext": "mIzRrwZAA8+WqRckG6gt1ji8HlEEJPSiV+TRBSR4GVr+FlAZlC5KvRriRF0=",
"iv": "lbwxXlAW2DS7+5jGz5Y1Kg==",
"version": "4.0.0",
"handle": "8e309bae-b3ec-4270-9b87-89f8697fe54f"
}