vania-janet/multiturn-rag-retrieval-data huggingface dataset:
1619](https://nvd.nist.gov/vuln/detail/CVE-2022-1619), [CVE-2022-1620](https://nvd.nist.gov/vuln/detail/CVE-2022-1620), [CVE-2022-1621](https://nvd.nist.gov/vuln/detail/CVE-2022-1621), [CVE-2022-2526](https://nvd.nist.gov/vuln/detail/CVE-2022-2526), [CVE-2022-2795](https://nvd.nist.gov/vuln/detail/CVE-2022-2795), [CVE-2022-35252](https://nvd.nist.gov/vuln/detail/CVE-2022-35252), [CVE-2022-36946](https://nvd.nist.gov/vuln/detail/CVE-2022-36946), [CVE-2022-38177](https://nvd.nist.gov/vuln/detail/CVE-2022-38177), [CVE-2022-38178](https://nvd.nist.gov/vuln/detail/CVE-2022-38178). 
 Kubernetes N/A N/A N/A 







 Change log for worker node fix pack 1.21.14_1578, released 12 September 2022 

The following table shows the changes that are in the worker node fix pack 1.21.14_1578. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.21.14_1578

 Component Previous Current Description
GPU device plug-in 4d3b934f 65e4401 Updated image for [CVE-2021-27919](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27919), [CVE-2020-28851](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28851), and [CVE-2020-28852](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28852). 
 IBM Cloud File Storage for Classic plug-in and monitor 388 389 Updated to use Go version 1.15.8. 
 Load balancer and load balancer monitor for IBM Cloud Provider 1165 1274 Fixed a bug that might cause version 2.0 network load balancers (NLBs) to crash and restart on load balancer updates. 







 Change log for worker node fix pack 1.17.17_1558, released 29 March 2021 

The following table shows the changes that are in the worker node fix pack 1.17.17_1558. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.17.17_1556

 Component Previous Current Description
Change log for worker node fix pack 4.10.12_1517_openshift, released 09 May 2022 

The following table shows the changes that are in the worker node fix pack 4.10.12_1517_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.10.10_1516_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A N/A 
 Red Hat OpenShift on IBM Cloud. 4.10.10 4.10.12 For more information, see the [change log](https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.htmlocp-4-10-12). 
 HAProxy f53b22 36b030 [CVE-2022-1271](https://nvd.nist.gov/vuln/detail/CVE-2022-1271), [CVE-2022-1154](https://nvd.nist.gov/vuln/detail/CVE-2022-1154), [CVE-2018-25032](https://nvd.nist.gov/vuln/detail/CVE-2018-25032). 







 Change log for fix pack 4.10.9_1515_openshift (master) and 4.10.10_1516_openshift (worker node), released 27 April 2022 



Changes since version 4.9.28_1536_openshift master and 4.9.29_1537_openshift worker node

 Component Previous Current Description 

 Calico v3.21.5 v3.22.2 See the [Calico release notes](https://docs.tigera.io/archive). 
 Calico Operator v1.23.7 v1.25.7 See the [Calico Operator release notes](https://github.com/tigera/operator/releases/tag/v1.25.7).
Change log for worker node fix pack 4.7.13_1521_openshift, released 9 June 2021 

The following table shows the changes that are in the worker node fix pack 4.7.13_1521_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.6.31_1545_openshift

 Component Previous Current Description 

 HA proxy 26c5cc 700dc6 Updated the image for [CVE-2021-27219](https://nvd.nist.gov/vuln/detail/CVE-2021-27219). 
 Red Hat OpenShift 4.6.31 4.7.13 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-13). The update resolves CVE-2021-30465 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6462567)). 
 TCP keepalive optimization for VPC N/A N/A Set the net.ipv4.tcp_keepalive_time setting to 180 seconds for compatibility with VPC gateways. 
 RHEL 7 Packages N/A N/A Updated worker node image with package updates for [CVE-2021-27219](https://nvd.nist.gov/vuln/detail/CVE-2021-27219). 







 Change log for master fix pack 4.7.12_1520_openshift, released 9 June 2021 

The following table shows the changes that are in the master fix pack patch update 4.7.12_1520_openshift. Master patch updates are applied automatically.



Changes since version 4.6.28_1543_openshift

 Component Previous Current Description 

 Calico v3.17.2 v3.19.1 See the [Calico release notes](https://docs.tigera.io/archive).
Change log for worker node fix pack 4.10.60_1571_openshift, released 5 June 2023 

The following table shows the changes that are in the worker node fix pack 4.10.60_1571_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.10.59_1569_openshift

 Component Previous Current Description 

 Red Hat OpenShift on IBM Cloud. 4.10.59 4.10.60 see [change logs](https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.htmlocp-4-10-60). 
 RHEL 7 Packages N/A N/A N/A 
 RHEL 8 Packages 4.18.0-477.10.1.el8_8 4.18.0-477.13.1.el8_8 Worker node kernel & package updates for [CVE-2023-22490](https://nvd.nist.gov/vuln/detail/CVE-2023-22490), [CVE-2023-23946](https://nvd.nist.gov/vuln/detail/CVE-2023-23946), [CVE-2023-25652](https://nvd.nist.gov/vuln/detail/CVE-2023-25652), [CVE-2023-25815](https://nvd.nist.gov/vuln/detail/CVE-2023-25815), [CVE-2023-29007](https://nvd.nist.gov/vuln/detail/CVE-2023-29007), [CVE-2023-32233](https://nvd.nist.gov/vuln/detail/CVE-2023-32233). 







 Change log for master fix pack 4.10.59_1570_openshift, released 25 May 2023
Change log for worker node fix pack 4.7.29_1531_openshift, released 13 September 2021 

The following table shows the changes that are in the worker node fix pack patch update 4.7.29_1531_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.7.24_1530_openshift

 Component Previous Current Description 

 OpenShift Container Platform 4.7.24 4.7.29 See the [Red Hat OpenShift release notes](http://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.html). 
 RHEL 7 Packages 3.10.0-1160.36.2.el7 3.10.0-1160.42.2.el7 Updated worker node image with package updates for [CVE-2021-25214](https://nvd.nist.gov/vuln/detail/CVE-2021-25214), [CVE-2020-27777](https://nvd.nist.gov/vuln/detail/CVE-2020-27777), [CVE-2021-22555](https://nvd.nist.gov/vuln/detail/CVE-2021-22555), [CVE-2021-29154](https://nvd.nist.gov/vuln/detail/CVE-2021-29154), [CVE-2021-29650](https://nvd.nist.gov/vuln/detail/CVE-2021-29650), [CVE-2021-32399](https://nvd.nist.gov/vuln/detail/CVE-2021-32399), [CVE-2021-3715](https://nvd.nist.gov/vuln/detail/CVE-2021-3715). 







 Change log for worker node fix pack 4.7.24_1530_openshift, released 30 August 2021
ibmcloud ac segment list [--limit LIMIT] [--offset OFFSET] [--sort SORT] [--tags TAGS] [--expand EXPAND] [--include INCLUDE]



 Command options 

--limit LIMIT (optional)
: Used for pagination. The number of records to retrieve.

--include INCLUDE (optional)
: Segment details to include the associated rules in the response.

--offset OFFSET (optional)
: Used for pagination. The number of records to skip.

--expand EXPAND (optional)
: Expanded view the segment details.

--tags TAGS (optional)
: Filter segments by a list of comma-separated tags.

--sort SORT (optional)
: Sort the details based on the specified attribute.





 Example 

To list all segments, run the following command:

ibmcloud ac segment list



 Output 

The command returns the following output:

name segment_id
India IBMers ibm_employees_01
IBM Employees ibm_employees









 ibmcloud ac segment create 

You can create a segment, by using the command:

ibmcloud ac segment create {--file FILE-PATH | --name NAME [--segment_id SEGMENT_ID] --description DESCRIPTION --tags TAGS --rules RULES}



 Command options 

--name NAME
: Segment name. Required field - input either as a flag or from file.

--segment_id SEGMENT_ID (optional)
: Segment ID. If this value is not provided, name will automatically become the ID. Optional field - input either as a flag or from file.

--description DESCRIPTION
: Description of the segment. Required field - input either as a flag or from file.

--rules RULES
: List of rules that determine whether the entity is part of the segment. Required field - input either as a flag or from file.

--tags TAGS
: Tags associated with the segment. Required field - input either as a flag or from file.

--file FILE
: Input through a file. File format Supported - JSON





 Example
--vault ([VaultReferenceInCreationRequest](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-cli-plugin-hpcs-cli-pluginuko-vault-reference-in-creation-request-example-schema))
: Required. The ID of the vault where the managed key is to be created.

--label (string)
: Required. The label of the key. The length must be between 1 and 255 characters. The value must match the regular expression /^[A-Za-z0-9._ /-]+$/.

--tags ([Tag[]](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-cli-plugin-hpcs-cli-pluginuko-tag-example-schema))
: Optional. Key-value pairs that are associated with the key. The length must be between 0 and 128 items.

--description (string)
: Optional. The description of the managed key. The length must be between 0 and 200 characters. The value must match the regular expression /(.|\n)/.
* Example

ibmcloud hpcs uko managed-key-create 
--uko-vault=5295ad47-2ce9-43c3-b9e7-e5a9482c362b 
--template-name=IBM-CLOUD-EXAMPLE-TEMPLATE 
--vault='{"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b"}' 
--label='IBM CLOUD KEY' 
--tags='[{"name": "first-tag", "value": "for-IBM-CLOUD"}]' 
--output json
* Output

The command returns the output similar to the following example:

ETag
2022-05-26T14:18:10Z
{
9],10],11],12],13],14],15],16],17],18],19],20],21],22],23],24],25],26]],"name":"rz","parameters":"theta"],"qasm_def":"gate rz(theta) q { U(0, 0, theta) q; }"},{"coupling_map":0],1],2],3],4],5],6],7],8],9],10],11],12],13],14],15],16],17],18],19],20],21],22],23],24],25],26]],"name":"sx","parameters":],"qasm_def":"gate sx q { U(pi/2, 3pi/2, pi/2) q; }"},{"coupling_map":0],1],2],3],4],5],6],7],8],9],10],11],12],13],14],15],16],17],18],19],20],21],22
: Collection ID. If this value is not provided, name will automatically become the ID. Optional field - input either as a flag or from file.

--description DESCRIPTION (optional)
: Description of the collection. Optional field - input either as a flag or from file.

--tags TAGS (optional)
: Tags associated with the collection. Optional field - input either as a flag or from file.

--file FILE
: Input through the file. File format Supported - JSON





 Example 

To create a collection with name sample using flags ([click here](https://cloud.ibm.com/docs/cli?topic=cli-app-configuration-cliac-fileinput) for using commands with --file flag), run the following command:

ibmcloud ac collection create --name sample --collection_id sampleId --description sampleDesc --tags sampleTag



 Output 

The command returns the following output:

collection_id sampleId
description sampleDesc
created_time 2021-01-18T08:15:45Z
updated_time 2021-01-18T08:15:45Z
name sample









 ibmcloud ac collection get 

You can get a collection, by using the command:

ibmcloud ac collection get --collection_id COLLECTION_ID [--expand EXPAND] [--include INCLUDE]



 Command options 

--collection_id COLLECTION_ID
: Collection ID for the collection.

--expand EXPAND (optional)
: Expanded view of the collection details.

--include INCLUDE (optional)
: Include feature and property details in the response.





 Example 

To get a collection with ID sampleId, run the following command:

ibmcloud ac collection get --collection_id sampleId



 Output 

The command returns the following output:

name sample
collection_id sampleId









 ibmcloud ac collection update 

You can update a collection, by using the command:

ibmcloud ac collection update {--file FILE-PATH | --name NAME --collection_id COLLECTION_ID --description DESCRIPTION --tags TAGS}
: Segment ID.

--include INCLUDE (optional)
: Instructs to include the feature and property details based on the segments association.





 Example 

To get a segment with ID ibm_employees, run the following command:

ibmcloud ac segment get --segment_id ibm_employees



 Output 

The command returns the following output:

segment_id description features created_time updated_time name attribute_name operator values
ibm_employees IBM Employees - 2021-02-02T19:04:22Z 2021-02-02T19:04:22Z IBM Employees email endsWith <Array>









 ibmcloud ac segment update 

You can update a segment, by using the command:

ibmcloud ac segment update {--file FILE-PATH | --name NAME --segment_id SEGMENT_ID --description DESCRIPTION --tags TAGS --rules RULES}



 Command options 

--name NAME
: Segment name. Required field - input either as a flag or from file.

--segment_id SEGMENT_ID
: Segment ID. Required field - input either as a flag or from file.

--description DESCRIPTION
: Description of the segment. Required field - input either as a flag or from file.

--rules RULES
: List of rules that determine whether the entity is part of the segment. Required field - input either as a flag or from file.

--tags TAGS
: Tags associated with the segment. Required field - input either as a flag or from file.

--file FILE
: Input through a file. File format Supported - JSON





 Example 

To update description a segment with ID ibm_employees using flags ([click here](https://cloud.ibm.com/docs/app-configuration-cli-plugin?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:
0cc6ddd7dafffdc5a955a640e678633c2710b174 refs/tags/5
0cc6ddd7dafffdc5a955a640e678633c2710b174 refs/tags/6
83f7a87ee59185eaeac554bd3abeebfd2c1b4ad8 refs/tags/8
0019d75d466bbdaba02ea979f3e094784a10b558 refs/tags/9
1914a125e76aa97c497f4bd2c2f455b58cf079b8 refs/tags/10
d9dd5d8553889ef24dff0678a3fcbae8aed3259b refs/tags/11
1914a125e76aa97c497f4bd2c2f455b58cf079b8 refs/tags/prod_latest



1. Select the inventory state to revert to refs/tags/8. The following command lists all the versions or commits between the current state (refs/tags/prod_latest) and the last known good state (refs/tags/8).



 /c/usr/devsecops/compliance-inventory (master)
$ git rev-list --no-merges HEAD...83f7a87ee59185eaeac554bd3abeebfd2c1b4ad8
67cc8babdff3e09c1f0e632f897798c1b5424f38
6fab5ce3d60590cd858206424ecfd7d3a8c9ceb4
22a575d48008299116ea426bdac45417d9df6238
* Flag: --if-modified-since TIMESTAMP



* Optional: Return the object only if its entity tag(ETag) is different from the ETAG specified, otherwise return a 304 (not modified).



* Flag: --if-none-match ETAG



* Optional: Return the object only if it has not been modified since the specified TIMESTAMP, otherwise return a 412 (precondition failed).



* Flag: --if-unmodified-since TIMESTAMP



* Optional: Downloads the specified RANGE bytes of an object. For more information about the HTTP Range header, [click here](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.htmlsec14.35).



* Flag: --range RANGE



* Optional: Sets the Cache-Control HEADER of the response.



* Flag: --response-cache-control HEADER



* Optional: Sets the Content-Disposition HEADER of the response.



* Flag: --response-content-disposition HEADER



* Optional: Sets the Content-Encoding HEADER of the response.



* Flag: --response-content-encoding HEADER



* Optional: Sets the Content-Language HEADER of the response.



* Flag: --response-content-language HEADER



* Optional: Sets the Content-Type HEADER of the response.



* Flag: --response-content-type HEADER



* Optional: Sets the Expires HEADER of the response.



* Flag: --response-expires HEADER



* Optional: The REGION where the bucket is present. If this flag is not provided, the program will use the default option specified in config.



* Flag: --region REGION



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT



* Optional: The location where to save the content of the object. If this parameter is not provided, the program uses the default location.



* Parameter: OUTFILE













 Find a bucket 



* Action: Determine the region and class of a bucket in an IBM Cloud Object Storage instance.
"log": {
"url": "https://acme.org/log.txt", // the link to where the actual log of the test is
"hash": "abc123", // the hash of the log file
},
"checksum_issues": 134, 132, 342], // link(s) to the issues representing missing or not matching checksums
"scan_issues": 123, 342, 453], // link(s) to the issues found by the scan (X-Ray)
"expired_issues": 134, 132, 342], // link(s) to the issues for which the grace period expired
"required": "yes"|"no"]// yes: this is an auditable step; no: this is a non auditable step
}, {
"evidence_type_id": "com.ibm.packages",
"version": "1.0.0",
"origin": {
"url":"https://us-south.git.cloud.ibm.com/open-toolchain/compliance-pipelines/-/blob/master/definitions/mytask.yaml", // where the task is taken from
"version": "423792" // commit id representing the task version used to produce the evidence
}
"toolchain_crn": "crn:v1:bluemix:public:toolchain:us-south:a/190e0b4ce4cd013159917665213ddc51:7467a214-f404-4e23-acab-2e57e935d138::" // CRN of the toolchain
"pipeline_id": "b1cfb6a4-813d-4fec-bbf7-ce662e8ce4e0", // the id of the pipeline that generated this piece of evidence
"pipeline_run_id": 12345, // this is the id of the pipeline run that generated this piece of evidence
Figure 13. A title is being labeled in the Smart Document Understanding tool

You labeled the title of the document successfully!
6. The rest of the text on the page can be indexed as part of the text field. Therefore, click Submit page.
7. The next page is the Table of contents for the document. Click the table_of_contents label, and then select all of the text on the page to label it. (You can click and drag the mouse to select all.) Click Submit page to move to the next page.

Zoom

![Shows the Table of contents that is being labeled in the SDU tool.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-label-toc.png)

Figure 14. A table of contents is being labeled in the Smart Document Understanding tool
8. The two headings on the page are subtitles. Click the subtitle label, and then select the headings.

This page has a footnote. As we noted earlier, the document has many footnotes where some important information is provided. Let's label the footnotes so we can include or exclude this type of information later. There is no footnote label, so we must add one.
9. From the Field labels list, click Create new. Add the name footnote as the label name. Click the color block repeatedly until you find a unique color to use for the label, and then click Create.

Zoom

![Shows the new label dialog.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-add-label.png)

Figure 15. New label dialog
10.
* Bold text indicates a column header
* Italic text indicates a row header
* Unstyled text indicates a body cell



The output from service represents the example's first body cell (that is, the first cell in row 3 with a value of 35.0%) as follows:

{
"tables": [ {
"location": {
"begin": 872,
"end": 5879
},
"text": "...",
"section_title": {
"text": "",
"location": {
"begin": 0,
"end": 0
}
},
"table_headers" : ],
"column_headers" : {
"cell_id" : "colHeader-1050-1082",
"location" : {
"begin" : 1050,
"end" : 1083
},
"text" : "Three months ended September 30,",
"text_normalized" : "Three months ended September 30,",
"row_index_begin" : 0,
"row_index_end" : 0,
"column_index_begin" : 1,
"column_index_end" : 2
}, {
"cell_id" : "colHeader-1270-1301",
"location" : {
"begin" : 1270,
"end" : 1302
},
"text" : "Nine months ended September 30,",
"text_normalized" : "Nine months ended September 30,",
"row_index_begin" : 0,
"row_index_end" : 0,
"column_index_begin" : 3,
"column_index_end" : 4
}, {
"cell_id" : "colHeader-1544-1548",
"location" : {
"begin" : 1544,
"end" : 1549
},
"text" : "2005",
archive: H4sIADXNg2IAA+3W326CMBQGcK59it555XbanraMq70KlOLIJhjqzPb2q6g3S9xiIi7T75eQlj+hDYcP6vvVuo/hMZsQJc6YsU2+t2NfsmKyyhHLjKRUSmbCTDmpo/e4KQchsqHvNz9d99v5f8of6l/3/jUMi8Puw+fq7XJj7ApsmU/WX2m7r7/j9Abs6s/W2kzQ5aZw2p3XfxuG2PZdIeZ6Poth2LY+xGImRLdsu49dR4h2VS5DsT/yHF9KZWxRSU02NCGkxJJ0FQVSoSlrn8Jba5eyrEsOT55dlduq9sY55sbrhlJpda7HG6/7YRP3YyxETkVOhz6zLtI2++unc/tO5b+84AfgrPyn4JM0pDXyfw3I/32bMvdH5+SfOK0TpdZWIv/XgPzftynX/Udn/f/NmH+l8P+/CuQfAAAAAAAAAAAAAOD2fAEPQbuiACgAAA==





 6. Populate the workload section 

Ensure that you do not miss the pipe symbol (|) if you are using a plain text contract.

workload: 
type: workload
compose:
: Collection ID. If this value is not provided, name will automatically become the ID. Optional field - input either as a flag or from file.

--description DESCRIPTION (optional)
: Description of the collection. Optional field - input either as a flag or from file.

--tags TAGS (optional)
: Tags associated with the collection. Optional field - input either as a flag or from file.

--file FILE
: Input through the file. File format Supported - JSON





 Example 

To create a collection with name sample using flags ([click here](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with --file flag), run the following command:

ibmcloud ac collection create --name sample --collection_id sampleId --description sampleDesc --tags sampleTag



 Output 

The command returns the following output:

collection_id sampleId
description sampleDesc
created_time 2021-01-18T08:15:45Z
updated_time 2021-01-18T08:15:45Z
name sample









 ibmcloud ac collection get 

You can get a collection, by using the command:

ibmcloud ac collection get --collection_id COLLECTION_ID [--expand EXPAND] [--include INCLUDE]



 Command options 

--collection_id COLLECTION_ID
: Collection ID for the collection.

--expand EXPAND (optional)
: Expanded view of the collection details.

--include INCLUDE (optional)
: Include feature and property details in the response.





 Example 

To get a collection with ID sampleId, run the following command:

ibmcloud ac collection get --collection_id sampleId



 Output 

The command returns the following output:

name sample
collection_id sampleId









 ibmcloud ac collection update 

You can update a collection, by using the command:
--description (string)
: Optional. The description of the managed key. The length must be between 0 and 200 characters. The value must match the regular expression /(.|\n)/.
* Example

ibmcloud hpcs uko managed-key-update 
--id=21a7498e-2ae4-47ee-85ac-a19bf64e92fa 
--uko-vault=eb66ebbd-7230-4cde-89bf-17282cda5faa 
--if-match=2022-05-26T14:18:10Z 
--description="updated description" 
--output json
* Output

The command returns the output similar to the following example:

ETag
2022-05-26T14:26:39Z
{
"id": "3dab42dc-6941-4841-8d27-4dabcc5aa09e",
"vault": {
"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b",
"name": "Test Vault Name",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
},
"template": {
"id": "93777bca-baef-4070-b9b5-a2e6079df1b4",
"name": "IBM-CLOUD-EXAMPLE-TEMPLATE"
},
"description": "IBM CLOUD key template description",
"label": "IBM CLOUD KEY",
"state": "active",
"size": "256",
"algorithm": "aes",
"verification_patterns": [
{