vania-janet/multiturn-rag-retrieval-data huggingface dataset:
curl -X GET -u "apikey:{apikey}" "{url}/v1/acoustic_customizations?language=en-US"

IBM Cloud Pak for Data

curl -X GET --header "Authorization: Bearer {token}" "{url}/v1/acoustic_customizations?language=en-US"

The credentials own two such models. The first model is awaiting data or is being processed by the service. The second model is fully trained and ready for use.

{
"customizations": [
{
"customization_id": "74f4807e-b5ff-4866-824e-6bba1a84fa97",
"created": "2016-06-01T18:42:25.324Z",
"updated": "2020-01-19T11:12:02.296Z",
"language": "en-US",
"versions":
"en-US_BroadbandModel.v2018-07-31",
"en-US_BroadbandModel.v2020-01-16"
],
"owner": "297cfd08-330a-22ba-93ce-1a73f454dd98",
"name": "Example model one",
"description": "Example custom acoustic model",
"base_model_name": "en-US_BroadbandModel",
"status": "pending",
"progress": 0
},
{
"customization_id": "8391f918-3b76-e109-763c-b7732faa3312",
"created": "2017-12-01T18:51:37.291Z",
"updated": "2017-12-02T19:21:06.825Z",
"language": "en-US",
"versions":
"en-US_BroadbandModel.v2017-11-15"
],
--environment_id ENVIRONMENT_ID (optional)
: Environment 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 environment. Optional field - input either as a flag or from file.

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

--color_code COLOR_CODE (optional)
: Color code to distinguish the environment. The Hex code for the color. Optional field - input either as a flag or from file.

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





 Example 

To create an environment with name Production_Environment 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 environment create --name Production_Environment --environment_id prodEnvironment --description sampleDesc --tags sampleTag --color_code "FF0000"



 Output 

The command returns the following output:

updated_time 2021-05-21T05:28:07.000Z
name Production_Environment
environment_id prodEnvironment
description sampleDesc
tags sampleTag
color_code FF0000
created_time 2021-05-21T05:28:07.000Z









 ibmcloud ac environment get 

You can get an environment detail, by using the command:

ibmcloud ac environment get --environment_id ENVIRONMENT_ID [--expand EXPAND] [--include INCLUDE]



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

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

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





 Example 

To get an environment with ID prodEnvironment, run the following command:
What is the order number?

![Shows the Ask for order number node details.](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/gs-ass-ask-for-order-number.png)
11. Click ![Close](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/close.png) to close the edit view.

Now, add another child node that informs the user that you are canceling the order.
12. Click the More![More options](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/kabob.png) icon on the Ask for order number node, and then select Add child node.
13. Type @order_number into the If assistant recognizes field of this node.
14. Open the context editor. Click the More![More options](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/kabob.png) icon, and select Open context editor.
15. Enter the following context variable name and value pair:



Order number context variable details

 Variable Value 

 $ordernumber 



The context variable value (<? @order_number.literal ?>) is a SpEL expression that captures the number that the user specifies that matches the pattern defined by the @order_number pattern entity. It saves it to the $ordernumber variable.
16. Add the following message in the response text field:
getDesignDocumentInformationOptions := service.NewGetDesignDocumentInformationOptions(
"recipes",
"recipesdd",
)

designDocumentInformation, response, err := service.GetDesignDocumentInformation(getDesignDocumentInformationOptions)
if err != nil {
panic(err)
}

b, _ := json.MarshalIndent(designDocumentInformation, "", " ")
fmt.Println(string(b))

The JSON response includes the following individual fields:

name
: Name or ID of design document.

view_index
: View Index

compact_running
: Indicates whether a compaction routine runs on the view.

disk_size
: Size in bytes of the view as stored on disk.

language
: Language that is used for defining views.

purge_seq
: The purge sequence that was processed.

signature
: MD5 signature of the views for the design document.

update_seq
: The update sequence of the corresponding database that was indexed.

updater_running
: Indicates whether the view is being updated.

waiting_clients
: Number of clients that are waiting on views from this design document.

waiting_commit
: Indicates whether the underlying database has outstanding commits that need to process.

See the following example response in JSON format:

{
"name" : "recipesdd",
"view_index": {
"compact_running": false,
"updater_running": false,
"language": "javascript",
"purge_seq": 10,
"waiting_commit": false,
"waiting_clients": 0,
"signature": "fc65594ee76087a3b8c726caf5b40687",
"update_seq": 375031,
"disk_size": 16491
}
}
Managing corpora 

The customization interface includes the POST /v1/customizations/{customization_id}/corpora/{corpus_name} method for adding a corpus to a custom language model. For more information, see [Add a corpus to the custom language model](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-languageCreateaddCorpus). The interface also includes the following methods for listing and deleting corpora for a custom language model.



 Listing corpora for a custom language model 

The customization interface provides two methods for listing information about the corpora for a custom language model:



* The GET /v1/customizations/{customization_id}/corpora method lists information about all corpora for a custom model.
* The GET /v1/customizations/{customization_id}/corpora/{corpus_name} method lists information about a specified corpus for a custom model.



Both methods return the name of the corpus, the total_words read from the corpus, and, for custom models based on previous-generation models, the number of out_of_vocabulary_words extracted from the corpus. The methods also list the status of the corpus. The status is important for checking the service's analysis of a corpus in response to a request to add it to a custom model.



* analyzed indicates that the service successfully analyzed the corpus. You can train the custom model with data from the corpus, or you can add additional corpora or words to the model.
* being_processed indicates that the service is still analyzing the corpus. The service cannot accept requests to add new corpora or words, or to train the custom model, until its analysis is complete.
* undetermined indicates that the service encountered an error while processing the corpus. The information that is returned for the corpus includes an error message that offers guidance for correcting the error.

For example, the corpus might be invalid, or you might have tried to add a corpus with the same name as an existing corpus. You can try to add the corpus again and include the allow_overwrite parameter with the request. You can also delete the corpus and then try adding it again.
The ID can be obtained by running the [ibmcloud resource service-instance command.](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance) One of --instance-id or --instance-name must be specified. The --instance-id and --instance-name options cannot be specified together on the same command invocation.

--instance-name INSTANCE_NAME (required), exclusive with --instance-id
: The name of the IBM Cloud Security and Compliance Center Workload Protection instance. This is the [name](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-provision) you specified when creating the instance. One of --instance-id or --instance-name must be specified. The --instance-id and --instance-name options cannot be specified together on the same command invocation.

--region REGION | -r REGION
: Name of the region, for example, us-south or eu-gb. If not specified, the region logged into, or targeted, will be used.

--output FORMAT
: Available output formats are JSON, YAML, or TABLE. If not specified, output will be returned in a tabular format.

--quiet | -q
: Suppress verbose messages.

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





 ibmcloud workload-protection compliance frameworks 

This command returns a list of available frameworks in your IBM Cloud Security and Compliance Center Workload Protection instance.

ibmcloud workload-protection compliance frameworks (--instance-id INSTANCE_ID | --instance-name INSTANCE_NAME) [--region REGION] [--output FORMAT] [--quiet]



 Frameworks command options 

See the [command options](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-workload-protection-compliance-cliss_compliance_options) for a description of each option.







 ibmcloud workload-protection compliance frameworks metadata
"secret_group_id" : "67d025e1-0248-418f-83ba-deb0ebfb9b4a",
"secret_id" : "67d025e1-0248-418f-83ba-deb0ebfb9b4a",
"secret_name" : "example-imported-certificate",
"secret_type" : "imported_cert",
"serial_number" : "38:eb:01:a3:22:e9:de:55:24:56:9b:14:cb:e2:f3:e3:e2:fb:f5:18",
"validity" : {
"not_after" : "2023-10-05T11:49:42Z",
"not_before" : "2022-06-27T11:58:15Z"
},
"version_custom_metadata" : {
"custom_version_key" : "custom_version_value"
}
} ],
"total_count" : 1
}







 ibmcloud secrets-manager secret-version 

Get a version of a secret by specifying the ID of the version. You can use the current or previous aliases to refer to the current or previous secret version.

A successful request returns the secret data that is associated with the specified version of your secret, along with other metadata.

ibmcloud secrets-manager secret-version --secret-id SECRET-ID --id ID



 Command options 

--secret-id (string)
: The ID of the secret. Required.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/.

--id (string)
: The ID of the secret version. Required.
Operations 



 Operation IDs 

Each operation in an OpenAPI document MUST have a unique operationId value. These values provide stable, meaningful handles for operations. For example, operationId values can be used as anchors in API documentation and function names in generated code.

Each operationId value SHOULD be a lower snake case string, with the convention of <verb>_<noun> where <verb> relates to the nature of the operation, and <noun> matches a resource type as it's represented in the path segment(s) for the operation and corresponds directly to the way the resource's [schemas are named](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-schemas). The plurality of the noun MUST agree with the number of resources operated on. For example, a POST /reticulated_splines operation to create a reticulated spline would have an operationId of create_reticulated_spline.

Parent resource types in a path SHOULD be included as qualifiers in the noun used for the operationId. For example, DELETE /farms/{farm_id}/barns/{id} would have an operationId of delete_farm_barn.

The success status codes in the examples below are defined for synchronous operations only. Refer to the section on [long-running operations](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-long-running-operations) for guidance on operations that return 202 Accepted.



 Standard operations 

The following conventions for operationId values SHOULD be used for standard operations on resources where possible.



Standard operations

 Verb Example method and path Success status code Recommended operation ID Description 

 list GET /albums 200 OK list_albums Retrieve a collection of albums 
 create POST /albums 201 Created create_album Create a new album 
 get GET /albums/{id} 200 OK get_album Retrieve the album identified by {id} 
 update PATCH /albums/{id} 200 OK update_album Update the album identified by {id} 
 delete DELETE /albums/{id} 204 No Content delete_album Delete the album identified by {id} 







 Resource replacement operations
<-- </section "id="section-cli-project-config-compliance-profile-example-schema" "> --><-- <section "id="section-cli-project-config-input-variable-example-schema" "> --> ProjectConfigInputVariable[ The following example shows the format of the ProjectConfigInputVariable[ object. {
"name" : "account_id",
"value" : "$configs].name\"account-stage\"].input.account_id"
} ] ! ! ] ]
<-- </section "id="section-cli-project-config-input-variable-example-schema" "> --><-- <section "id="section-cli-project-config-prototype-example-schema" "> --> ProjectConfigPrototype[ The following example shows the format of the ProjectConfigPrototype[ object. {
"name" : "common-variables",
"labels" : ],
"description" : "exampleString",
"authorizations" : {
"trusted_profile" : {
"id" : "exampleString",
"target_iam_id" : "exampleString"
},
"method" : "exampleString",
"api_key" : "exampleString"
},
"compliance_profile" : {
"id" : "exampleString",
"instance_id" : "exampleString",
"instance_location" : "exampleString",
"attachment_id" : "exampleString",
"profile_name" : "exampleString"
},
It is recommended to specify the key ring ID for a more optimized request. <br>Note: The key ring ID of keys that are created without an x-kms-key-ring header is: default. <br>For more information, see [Grouping keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-grouping-keys). 
 correlation_ID The unique identifier that is used to track and correlate transactions. 
 encrypted_data_key Required. The ciphertext value that was returned by the original wrap operation. 
 additional_data OptionalThe additional authentication data (AAD) that is used to further secure the key. Each string can hold up to 255 characters. If you supplied AAD for the initial wrap call, you must specify the same AAD during the subsequent unwrap or rewrap calls. <br> <br>Important: The Key Protect service does not save additional authentication data. If you supply AAD, save the data to a secure location to ensure that you can access and provide the same AAD during subsequent unwrap or rewrap requests. 



The newly wrapped data encryption key, original key version (keyVersion) that is associated with the supplied ciphertext and latest key version ( rewrappedKeyVersion) associated with the new ciphertext is returned in the response entity-body. The following JSON object shows an example returned value.

{
"ciphertext": "eyJjaX ... h0Ijoi ... c1ZCJ9",
"keyVersion": {
"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
For more information, see [Adding integrations](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-integration-add).





 Where is the Assistant ID found in the new product experience? 

The assistant ID can be found in Assistant settings.

In Assistant settings, the assistant ID is in the Assistant IDs and API details section.



* What is the new IBM Watson® Assistant experience?

 What is the new IBM Watson® Assistant experience? 

The new Watson Assistant is an improved way to build, publish, and improve virtual assistants. In the new experience, you use actions to build conversations. Actions are a simple way for anyone to create assistants. For more information, see the [Getting Started guide](https://www.ibm.com/blogs/watson/2021/12/getting-started-with-the-new-watson-assistant-part-i-the-build-guide/) or the [documentation](https://cloud.ibm.com/docs/watson-assistant) for the new experience.
* Why can't I see the assistants that I made with classic Watson Assistant in the new experience?

 Why can't I see the assistants that I made with classic Watson Assistant in the new experience? 

The new Watson Assistant is a clean slate in the same IBM Cloud instance as your classic experience. Assistants that you created in one experience don't appear in the other. However, you can switch back and forth between experiences without losing any work. For more information, see [Switching the experience](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-welcome-new-assistantwelcome-new-assistant-switch-experience).
* What happens when I switch between the classic and new Watson Assistant experiences?

 What happens when I switch between the classic and new Watson Assistant experiences? 

The assistants that you create in one experience don't transfer to the other. However, you can switch experiences, return to your work, and create or use assistants. You don't lose anything by switching. Changing experiences doesn't affect other users in the same instance.
By default, the id format (the --format flag) prints the internal ID of the created asset. With the json format, the whole asset is going to be printed, as a JSON object.

Running the command to add a Git commit:

$ cocoa locker asset add 'https://github.ibm.com/foo/bar.gitaaaaaaaabbbbbbbbccccccccddddddddeeeeeeee' --details tag=v1.2.3

Example output:

b5bbbbb55555b5555b555b55b5555bb5b555b5b555bb5b55bbb5555fbbbbb

Running the command to add a Docker image:

$ cocoa locker asset add docker://us.icr.io/foo/bar:v1.2.3@sha256:0000000011111111222222223333333344444444555555556666666677777777 --origin "job_name=my job" --related https://github.ibm.com/foo/bar.gitaaaaaaaabbbbbbbbccccccccddddddddeeeeeeee 
--format json

Example output:

{
"version": "1",
"id": "0000000011111111222222223333333344444444555555556666666677777777",
"uri": "docker://us.icr.io/foo/bar:v1.2.3@sha256:0000000011111111222222223333333344444444555555556666666677777777",
"origin": {
"job_name": "my job",
The virtual server instance is automatically assigned an instance identifier (ID), which includes the SMBIOS system-uuid as a portion of the ID, when the instance is created. IDs are immutable, globally unique, and never reused, so the ID uniquely identifies a particular instantiation of a virtual server instance across all of IBM Cloud. The ID, including the SMBIOS system-uuid portion, is static and persists for the lifecycle of the virtual server instance until that virtual server instance is deleted.

For more information, including how to retrieve this information from within your virtual server, see [Retrieving the virtual server instance identifier](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instancesretrieve-VSI-instance-identifer) section in Managing virtual server instances.
* Can I use the same operating system image for more than one account?

Yes, when you create a custom image for IBM Cloud VPC, you can import those images into a private catalog for use among multiple accounts. A private catalog provides a way for you to manage access to products for multiple accounts, if those accounts are within the same enterprise. You must first complete all the steps to import the custom image into IBM Cloud VPC before you can import the image into a private catalog. For more information about private catalog considerations and limitations, see [Getting started with custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-about-custom-images).
* Can I use a custom image in a private catalog with an instance group?

Yes, you can use a custom image in a private catalog with an instance group. However, you must first create a service-to-service policy to globalcatalog-collection.instance.retrieve before you can create the instance group. For more information, see [Using a custom image in a private catalog with an instance group](https://cloud.ibm.com/docs/vpc?topic=vpc-private-catalog-image-instance-group&interface=ui).
* Can I change the boot volume associated with my resource group after creating the resource group?
OpsGenie OPSGENIE 







 version (integer) 

Version of an notification.

The version changes every time you update an notification.

The version is used for optimistic locking.







 Query parameters 



 notificationId (integer) 

ID of an notification.





 from (long) 

Defines the start timestamp, in microseconds, that is used when you request information about notifications that are defined.





 to (long) 

Defines the end timestamp, in microseconds, that is used when you request information about notifications that are defined.
* IKE_POLICY_ID: The unique identifier of the VPN IKE policy



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







 ibmcloud pi vpn-ipsec-policies 



 List all IPSec policies 

ibmcloud pi vpn-ipsec-policies [--json]

Options



* --json: Format output in JSON



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







 ibmcloud pi vpn-ipsec-policy 



 View details of a VPN IPSec policy 

ibmcloud pi vpn-ipsec-policy IPSEC_POLICY_ID [--json]



* IPSEC_POLICY_ID: The unique identifier of the VPN IPSEC policy



Options



* --json: Format output in JSON



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







 ibmcloud pi vpn-ipsec-policy-add 



 Add a VPN IPSec policy 

ibmcloud pi vpn-ipsec-policy-add IPSEC_POLICY_NAME --authentication AUTHENTICATION --encryption ENCRYPTION --dh-group DH_GROUP --key-lifetime SECONDS [--pfs] [--json]



* IPSEC_POLICY_NAME: The name of the VPN IPSEC policy. The maximum name length is 47 characters



Options



* --authentication value: Authentication encryption type of the IPSec policy. Valid values are 'hmac-sha-256-128', 'hmac-sha1-96', 'none'.
* --encryption value: Connection encryption policy of the IPSec policy. Valid values are 'aes-256-cbc', 'aes-192-cbc', 'aes-128-cbc', 'aes-256-gcm', 'aes-192-gcm', 'aes-128-gcm', '3des-cbc'.
Command options 

RESOLVER_ID
: The ID of custom resolver.

RULE_ID
: The ID of custom resolver forwarding rule.

-i, --instance
: Instance name or ID. If not set, the context instance specified by dns instance-target INSTANCE is used.

--output
: Specify output format. Currently, json is the only supported format.





 Examples 

Get a forwarding rule 9a234ede-c2b6-4c39-bc27-d39ec139ecdb in custom resolver f1aba936b94213e5b8dca0c0dbf1f9cc for instance dns-demo.

ibmcloud dns custom-resolver-forwarding-rule f1aba936b94213e5b8dca0c0dbf1f9cc 9a234ede-c2b6-4c39-bc27-d39ec139ecdb -i "dns-demo"







 ibmcloud dns custom-resolver-forwarding-rules 

List custom resolver forwarding rules for a service instance.

ibmcloud dns custom-resolver-forwarding-rules RESOLVER_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

RESOLVER_ID
: The ID of custom resolver.

-i, --instance
: Instance name or ID. If not set, the context instance specified by dns instance-target INSTANCE is used.

--output
: Specify output format. Currently, json is the only supported format.





 Examples 

List forwarding rules in custom resolver f1aba936b94213e5b8dca0c0dbf1f9cc for instance dns-demo.

ibmcloud dns custom-resolver-forwarding-rules f1aba936b94213e5b8dca0c0dbf1f9cc -i "dns-demo"







 ibmcloud dns custom-resolver-forwarding-rule-delete 

Delete a custom resolver forwarding rule for a service instance.