vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Each call to an extension creates a separate set of response variables. If your action calls the same extension multiple times from different steps, make sure you select the variables from the correct step.

Each variable represents a value from the response body. To make it easy to access these values, data is extracted from complex, nested objects and mapped to individual response variables. The name of each variable reflects its location within the response body (for example, body.name or body.customer.address.zipcode).

For example, this action step uses an expression to check the availability property in an extension response:

![Extension variable in step condition](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/response-expression-condition.png)

If a response variable contains an array, you can write an expression that uses array methods to access the elements of the array. For example, you might use the contains() method in a step condition to test whether the array contains a particular value, or the join() method to format data from the array as a string you can include in an assistant response. For more information about array methods, see [Array methods](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-expression-methods-actionsexpression-methods-actions-arrays).





 Checking success or failure 

You might want your assistant to be able to handle errors that occur when calling a custom extension. You can do this by checking the Ran successfully response variable that is returned along with the response from the call to the extension. This variable is a boolean (true or false) value.

If you define step conditions that check the Ran successfully variable, you can create steps that enable your assistant to respond differently depending on whether the call to the extension succeeded. (For more information about step conditions, see [Step conditions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-step-conditions).)

The following example shows a step condition that checks for a failure from an extension in step 3.
A custom voice is a unique voice that is based on audio training data that the customer provides. IBM can train a custom voice with as little as one hour of training data.

To request a custom voice or for more information, complete and submit this [IBM Request Form](https://form.asana.com/?k=CBuXK1uwlAf5ek6FwB6mcg&d=8612789739828).







 Using Tune by Example 

The Tune by Example feature lets you control how specified text is spoken by the service. The feature lets you dictate the intonation, cadence, and stress of the synthesized text. You create a custom prompt by providing a sample recording that speaks the text as you want to hear it. The service then duplicates the qualities of the recorded speech with its voices when you synthesize the prompt.

The feature provides a simpler mechanism than standard SSML for modifying how speech is synthesized. Tune by Example eliminates the need for complex SSML by letting you record text as you want it to be spoken rather than requiring you to emulate the intended prosody with SSML.

You can increase the quality of custom prompts by associating speaker models with those users who speak the prompts. You create a speaker model by providing an audio sample of a user's voice. The service trains itself on the voice to help it produce higher-quality prompts for that speaker.

For more information about Tune by Example, custom prompts, and speaker models, see [Understanding Tune by Example](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-tbe-intro).

The Tune by Example feature is beta functionality that is supported only for US English custom models and voices.





 Using software development kits 

SDKs are available for the Text to Speech service to simplify the development of speech applications. The SDKs support many popular programming languages and platforms.



* For a complete list of SDKs and links to the SDKs on GitHub, see [Watson SDKs](https://cloud.ibm.com/docs/text-to-speech?topic=watson-using-sdks).
The v1 events and feedback API (/v1/events) is not available in v2.





 Credentials 

The v1 credentials API (/v1/environments/{environment_id}/credentials) is not available in v2. The function is available from the v2 product user interface.





 Gateway configuration 

The v1 gateways API (/v1/environments/{environment_id}/gateways) is not available in v2. The function is available from the v2 product user interface. For more information, see [Installing IBM Secure Gateway for on-premises data](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-sourcesgatewaypublic).





 Status codes 

For almost every API method, the status codes that are returned for v2 requests are different from the status codes that are returned for v1 requests.
Date: Tue, 18 Feb 2020 07:16:56 GMT
Content-Length: 1524
...
...
X-Check-Cacheable: YES
Show more

If Akamai debug headers are returned, and the response code and content match the content that is returned from the wanted domain, the wildcard CDN traffic works. See the Troubleshooting section for further debugging tips.

Along with the basic function verification, it is recommended that you verify more functions that you plan to use; for example, caching, multiple origins, purge, and so on.
2. Create a provider.tf file and add an empty provider block.

provider "ibm" {}
3. Set the environment variables on your local machine.

export IC_API_KEY="<ibmcloud_api_key>"
export IAAS_CLASSIC_USERNAME="<classic_username>"
export IAAS_CLASSIC_API_KEY="<classic_api_key>"
4. Initialize the Terraform CLI.

terraform init









 Creating multiple provider configurations 

You can add multiple provider configurations within the same Terraform on IBM Cloud configuration file to create your IBM Cloud resources with different provider parameters.

Creating multiple provider configurations is useful when you want to use different input parameters, such as different regions, zones, infrastructure generations, or accounts to create the IBM Cloud resources in your Terraform on IBM Cloud configuration file. For more information, see [Multiple Provider Instances](https://developer.hashicorp.com/terraform/language/providers/configuration).



1. In your Terraform on IBM Cloud configuration or provider.tf file, create multiple provider blocks with the same provider name. The provider configuration without an alias is considered the default provider configuration and is used for every resource where you do not specify a specific provider configuration. Any more provider configurations must include an alias so that you can reference this provider from your resource definition.

provider "ibm" {
ibmcloud_api_key = var.ibmcloud_api_key
region = "us-south"
}

provider "ibm" {
alias = "east"
ibmcloud_api_key = var.ibmcloud_api_key
region = "us-east"
}
2. In your resource definition, specify the provider configuration that you want to use. If you do not specify a provider, the default provider configuration is used.

resource "ibm_container_cluster" "cluster" {
provider = ibm.east
...
}







 Configuring non-default cloud service endpoints 

The IBM Cloud Provider plug-in for Terraform can be configured to use non-default IBM Cloud service endpoints.
For more information, about how to create an API key, see [Creating an API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key). You can specify the API key in the provider block or retrieve the value from the IC_API_KEY or IBMCLOUD_API_KEY environment variables. If both environment variables are defined, IC_API_KEY takes precedence. 
 ibmcloud_timeout Optional The number of seconds that you want to wait until the IBM Cloud API is considered unavailable. The default value is 60. You can specify the timeout in the provider block or retrieve the value from the IC_TIMEOUT or IBMCLOUD_TIMEOUT environment variables. If both variables are specified, IC_TIMEOUT takes precedence. 
 region Optional The IBM Cloud region where you want to create your resources. If this value is not specified, us-south is used by default. You can specify the region in the provider block or retrieve the value from the IBMCLOUD_REGION or IC_REGION environment variables. If both environment variables are specified, IC_REGION takes precedence. 
 resource_group Optional The ID of the resource group that you want to use for your IBM Cloud resources. To retrieve the ID, run ibmcloud resource groups. You can specify the resource group in the provider block or retrieve the value from the IC_RESOURCE_GROUP or IBMCLOUD_RESOURCE_GROUP environment variables. If both environment variables are defined, IC_RESOURCE_GROUP takes precedence. 



For more information on how to use environment variables, see [Using environment variables](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-referenceenv-vars).

You can [add multiple provider configurations within the same Terraform on the IBM Cloud configuration file](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-referencemultiple-providers) to create your IBM Cloud resources with different provider parameters.
[Check mark](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/checkmark.svg) 
 iaas_classic_username ![Check mark](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/checkmark.svg) 
 iaas_classic_api_key ![Check mark](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/checkmark.svg) 
 function_namespace ![Check mark](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/checkmark.svg) 
 zone ![Check mark](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/checkmark.svg) <br>For multi-zone regions only 







 Supported input parameters 

Review what parameters you can set in the provider block of your Terraform on IBM Cloud configuration file. For more information, about the IBM Cloud provider input parameters, see [IBM Cloud](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docsargument-reference).



Supported input parameters in configuration file
Event Notifications CLI commands 



 ibmcloud event-notifications init 

Set the instance that you'll we working on by using the following command:

ibmcloud event-notifications init [--instance-id INSTANCE-ID]



 Command options 

--instance-id (string)
: Unique identifier for IBM Cloud Event Notifications instance.

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







 ibmcloud event-notifications environment variables set 



* export IBMCLOUD_EN_ENDPOINT variable to set the Event Notifications region public endpoint.



* Dallas:https://us-south.event-notifications.cloud.ibm.com/event-notifications
* London:https://eu-gb.event-notifications.cloud.ibm.com/event-notifications
* Sydney:https://au-syd.event-notifications.cloud.ibm.com/event-notifications
* Frankfurt:https://eu-de.event-notifications.cloud.ibm.com/event-notifications



* export IBMCLOUD_EN_ENDPOINT variable to set the Event Notifications region private endpoint.



* Dallas:https://private.us-south.event-notifications.cloud.ibm.com/event-notifications
* London:https://private.eu-gb.event-notifications.cloud.ibm.com/event-notifications
* Sydney:https://private.au-syd.event-notifications.cloud.ibm.com/event-notifications
* Frankfurt:https://private.eu-de.event-notifications.cloud.ibm.com/event-notifications



* export EVENT_NOTIFICATIONS_API_KEY variable to set the Event Notifications instance apikey.







 ibmcloud event-notifications show
Washington DC https://us-east.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid} 
 London https://eu-gb.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid} 
 Sydney https://au-syd.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid} 







 Private endpoints 

If you need to manage your IBM Cloud App Configuration resources over a private network, see the following table to determine the API endpoints to use when you connect to the IBM Cloud App Configuration API.



Table 2. Private endpoints

 Location Endpoint URL 

 Dallas https://private.us-south.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid} 
 Washington DC https://private.us-east.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid} 
 London https://private.eu-gb.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid} 
 Sydney https://private.au-syd.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid}
ibmcloud atracker setting update [--metadata-region-primary REGION] [--metadata-region-backup REGION] [--default-targets TARGET] [--permitted-target-regions REGIONS] [--private-api-endpoint-only ( TRUE | FALSE )] [--output FORMAT] [--force]



 Command options 

default-targets
: Is a list of target IDs. If no routing rules cause events to be sent to other targets, these targets will received the events. TARGETS is a comma-separated list of target IDs.

permitted-target-regions
: Is the list of regions that can be used to define a target. REGIONS is a comma-separated list of regions. A maximum of two permitted target regions can be specified.

metadata-region-primary
: Specify the REGION where the metadata associated with route and target definitions is stored.

metadata_region_backup
: Is the region where the metadata associated with route and target definitions is stored as a backup location.

private-api-endpoint-only
: Specifies whether nor not a private endpoint can be used. If true only a private endpoint can be used.

--output FORMAT
: If JSON specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

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







 ibmcloud atracker migration start 

Use this command to migrate all targets and routes for an IBM account from a V1 API configuration to a V2 API configuration.

ibmcloud atracker migration start





 ibmcloud atracker migration status 

Use this command to get the status of an in-progress migration.

ibmcloud atracker migration status
[Learn more about the public access group](https://cloud.ibm.com/docs/account?topic=account-publicpublic).





 12 March 2019 

Multifactor authentication for users with federated IDs
: Account owners or users assigned the administrator role for the billing account management service can enable multifcator authentication (MFA) for all users in their account. Federated users who use their corporate or enterprise single sign-on ID can now be required to authenticate by using MFA for logging in to IBM Cloud. For more information about this feature enhancement and what you need to know about enabling MFA for your account, see [Introducing MFA for IBM Cloud Users with Federated ID](https://www.ibm.com/cloud/blog/introducing-mfa-for-ibm-cloud-users-with-federated-id) .







 December 2018 



 31 December 2018 

New appdomain.cloud host name option
: A new host name option .appdomain.cloud is available on cloud.ibm.com.

Previously, the mybluemix.net domain was used for hosting apps in various deployment targets, such as IBM Cloud Kubernetes Service or Cloud Foundry. Any apps that are hosted on mybluemix.net are not impacted.

The subdomain for Cloud Foundry apps is cf.appdomain.cloud. The subdomain for apps that you deploy to IBM Cloud Kubernetes Service is containers.appdomain.cloud.







 November 2018 



 30 November 2018 

New Cloud Foundry API endpoints
: The legacy api..bluemix.net Cloud Foundry API endpoints are still available for compatibility with earlier versions. However, you can update scripts and infrastructure automation to use the following new Cloud Foundry API endpoints for your region:



* api.us-south.cf.cloud.ibm.com (previously api.ng.bluemix.net)
* api.eu-gb.cf.cloud.ibm.com (previously api.eu-gb.bluemix.net)
* api.us-east.cf.cloud.ibm.com (previously api.us-east.bluemix.net)
Account management IBMCLOUD_ACCOUNT_MANAGEMENT_API_ENDPOINT N/A 
 API Gateway IBMCLOUD_API_GATEWAY_ENDPOINT N/A 
 Certificate manager IBMCLOUD_CERTIFICATE_MANAGER_API_ENDPOINT N/A 
 Cloud Foundry IBMCLOUD_MCCP_API_ENDPOINT N/A 
 Cloud functions IBMCLOUD_NAMESPACE_API_ENDPOINT N/A 
 CIS IBMCLOUD_CIS_API_ENDPOINT N/A 
 Containers IBMCLOUD_CS_API_ENDPOINT [Docs](https://cloud.ibm.com/docs/containers?topic=containers-plan_clusters) 
 Content Catalog IBMCLOUD_CATALOG_MANAGEMENT_API_ENDPOINT N/A 
 Container Registry IBMCLOUD_CR_API_ENDPOINT N/A 
 COS config IBMCLOUD_COS_CONFIG_ENDPOINT N/A 
 COS-S3 IBMCLOUD_COS_ENDPOINT N/A 
 Direct Link IBMCLOUD_DL_PROVIDER_API_ENDPOINT N/A 
 Enterprise Management IBMCLOUD_ENTERPRISE_API_ENDPOINT N/A 
 Global tagging IBMCLOUD_GT_API_ENDPOINT [Endpoint URLs](https://cloud.ibm.com/apidocs/taggingendpoint-url) 
 HPCS IBMCLOUD_HPCS_API_ENDPOINT N/A 
 IAM IBMCLOUD_IAM_API_ENDPOINT [Endpoint URLs](https://cloud.ibm.com/apidocs/iam-access-groupsendpoint-urls) 
 IAMPAP IBMCLOUD_IAMPAP_API_ENDPOINT N/A 
 ICD IBMCLOUD_ICD_API_ENDPOINT [Docs](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint) 
 Key protect IBMCLOUD_KP_API_ENDPOINT [Docs](https://cloud.ibm.com/docs/key-protect?topic=key-protect-private-endpoints)
: The timeout value for HTTP requests in seconds. The default value is 60 seconds.

--locale<
: Set a default locale. If no value is specified, the previous locale is deleted.

--trace
: Trace HTTP requests to the terminal or specified file. Valid values are true or false.

You can specify only one of the options at a time.





 Examples 

Set HTTP request timeout to 30 seconds:

ibmcloud config --http-timeout 30

Enable trace output for HTTP requests:

ibmcloud config --trace true

Trace HTTP requests to the /home/usera/my_trace file:

ibmcloud config --trace /home/usera/my_trace

Disable color output:

ibmcloud config --color false

Set the locale to zh_Hans:

ibmcloud config --locale zh_Hans

Clear the locale settings:

ibmcloud config --locale CLEAR







 ibmcloud login 

Log in to the IBM Cloud CLI:

ibmcloud login [-a API_ENDPOINT] [--sso] [-u USERNAME] [-p PASSWORD] [--apikey KEY | @KEY_FILE] [--cr-token (TOKEN | @CR_TOKEN_FILE) | --vpc-cri] [--profile PROFILE_ID | PROFILE_NAME | PROFILE_CRN] [-c (ACCOUNT_ID | ACCOUNT_OWNER_USER_ID) | --no-account] [--accept] [-g (RESOURCE_GROUP_NAME | RESOURCE_GROUP_ID)] [-r REGION | --no-region] [--vpc]



 Prerequisites 

None.





 Command options 

-a API_ENDPOINT
: The API endpoint. For example, cloud.ibm.com. Or, use private.cloud.ibm.com to log in by using a private endpoint. Using this flag saves the API endpoint to the configuration file.

--sso
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 







 Compute serverless services 

Americas

Asia Pacific

Europe



Table 4. Compute serverless services integration in Americas locations

 Service Dallas (us-south) Washington (us-east) Toronto (ca-tor) Sao Paulo (br-sao) 

 Cloud Functions ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Code Engine ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 







 Container services 

IBM Cloud Container Registry
: You can track how users and applications interact with the IBM Cloud Container Registry service. For information about the locations where the automatic collection of Container Registry service events is enabled, see [Auditing events for IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-at_eventsat_events_locations).

IBM Cloud Kubernetes Service
: For IBM Cloud Kubernetes Service, see [Viewing your cluster events](https://cloud.ibm.com/docs/containers?topic=containers-at_eventsat-ui).

IBM Cloud Satellite
--cpu
: The amount of CPU set for the instance of the function. For valid values, see [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo). This value is optional. The default value is 0.25.

--env, -e
: Set environment variables in the function. Must be in NAME=VALUE format. This action adds a new environment variable or overrides an existing environment variable. Specify one environment variable per --env option; for example, --env envA=A --env envB=B. This value is optional.

--env-cm, --env-from-configmap
: Set environment variables from the key-value pairs that are stored in this configmap by using one of the following ways:



* To add environment variables for all keys in a configmap that is named configmapName, use the value configmapName. You can modify the environment variable names by specifying a prefix when referencing the configmap. To specify a prefix, use the value PREFIX=CONFIGMAP_NAME. Each resulting environment variable has the format <PREFIX><NAME_OF_KEY_IN_CONFIGMAP>. For example, to set the prefix for all variable names of keys in configmap configmapName to CUSTOM_, use the value CUSTOM_=configmapName. If the configmap configmapName contains KEY_A, the environment variable name is CUSTOM_KEY_A.
* To add environment variables for individual keys, use the format NAME:KEY_A,KEY_B. For example, to add an environment variable for a single key key1 in a configmap that is named configmapName, use the value configmapName:key1.
After creating an endpoint gateway for DNS Services, you must use the private endpoint's FQDN when setting the service's FQDN during construction of the DNS Services gateway service object.

api.private.dns-svcs.cloud.ibm.com

For examples of setting the service's FQDN for the specific SDK language, see [SDK API examples](https://cloud.ibm.com/apidocs/dns-svcs?code=goauthentication).





 Using the VPE with Terraform 

If you plan to access the DNS Services service using Terraform, make sure to set the IBMCLOUD_PRIVATE_DNS_API_ENDPOINT environment variable to api.private.dns-svcs.cloud.ibm.com. For example:

export IBMCLOUD_PRIVATE_DNS_API_ENDPOINT=api.private.dns-svcs.cloud.ibm.com

For more information, see [DNS Services resources and data sources](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-resources-datasource-listibm-dns-service_rd).