vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [API Endpoints](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-endpointsendpoints_api). 



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. For example, you can multiple providers so that you can 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://www.terraform.io/docs/language/providers/configuration.html).



 Option 1. Creating a static provider.tf file 

You can declare the input parameters in the provider block directly.

Because the provider block includes sensitive information, do not commit this file into a public source repository. To add version control to your provider configuration, use a local [terraform.tfvars file](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-terraform-streamingtf-variables).

Create a provider.tf file and specify the input parameters that are required for your resource or data source.

provider "logdna" {
servicekey = "<service_key>"
url = "<API_ENDPOINT>"
}

Where





 Option 2. Referencing credentials from a Terraform tfvars file 

You can store sensitive information, such as credentials, in a local terraform.tfvars file and reference these credentials in your provider block.

Do not commit the terraform.tfvars into a public source repository.
This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 300.





 Example 

ibmcloud ce fn bind --name myfunction --service-instance my-object-storage





 Example output 

Binding service instance...
Status: Done
OK







 ibmcloud ce function create 

Create a function.

ibmcloud ce function create --name FUNCTION_NAME [--build-commit BUILD_COMMIT] [--build-context-dir BUILD_CONTEXT_DIR] [--build-git-repo-secret BUILD_GIT_REPO_SECRET] [--build-source BUILD_SOURCE] [--build-strategy BUILD_STRATEGY] [--build-timeout BUILD_TIMEOUT] [--code-bundle CODE_BUNDLE] [--code-bundle-secret CODE_BUNDLE_SECRET] [--cpu CPU] [--env ENV] [--env-from-configmap ENV_FROM_CONFIGMAP] [--env-from-secret ENV_FROM_SECRET] [--force] [--inline-code INLINE_CODE] [--main MAIN] [--maxexecutiontime MAXEXECUTIONTIME] [--memory MEMORY] [--no-wait] [--output OUTPUT] [--quiet] [--runtime RUNTIME] [--runtime-secret RUNTIME_SECRET] [--runtime-type RUNTIME_TYPE] [--wait] [--wait-timeout WAIT_TIMEOUT]



 Command Options 

-n, --name
: The name of the function. Use a name that is unique within the project.



* The name must begin with a lowercase letter.
* The name must end with a lowercase alphanumeric character.
* The name must be 63 characters or fewer and can contain lowercase letters, numbers, and hyphens (-).



This value is required.

--runtime, -r
: The runtime to use for the function.
}
}
* The following example shows format of the DestinationConfig object for MS Teams destination.

{
"params" : {
"url" : "https://xyz.webhook.office.com"
}
}
* The following example shows format of the DestinationConfig object for IBM Cloud® Functions destination.

{
"params" : {
"url" : "https://www.ibmcfendpoint.com",
"api_key" : "cffunctionnamespaceserviceidapikey"
}
}
* The following example shows format of the DestinationConfig object for PagerDuty destination.

{
"params" : {
"routing_key" : "routingkeytoconnecttoPD",
"api_key" : "cffunctionnamespaceserviceidapikey"
}
}
* The following example shows the format of the DestinationConfig object for webhook.

{
"params" : {
"url" : "exampleString",
"verb" : "get",
"custom_headers" : { },
"sensitive_headers" : [ "exampleString" ]
}
}
* The following example shows the format of the DestinationConfig object for push_android destination.

{
"params" : {
"project_id" : "6232305230320",
"private_key" : "36e21epfweort823or8rt832pr8p2r832pr82pr382r8f",
"client_email" : "testuser.123@gmail.com",
"pre_prod" : true // Set to true in case of configuring Destination as pre-prod Destination (pre_prod destination can only be configured for Standard plan)
}
}
* The following example shows the format of the DestinationConfig object for ServiceNow destination.

{
"params" : {
For more information, see [API Endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_api). 



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. For example, you can multiple providers so that you can 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://www.terraform.io/docs/language/providers/configuration.html).



 Option 1. Creating a static provider.tf file 

You can declare the input parameters in the provider block directly.

Because the provider block includes sensitive information, do not commit this file into a public source repository. To add version control to your provider configuration, use a local [terraform.tfvars file](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-terraform-service-keystf-variables).

Create a provider.tf file and specify the input parameters that are required for your resource or data source.

provider "logdna" {
servicekey = "<service_key>"
url = "<API_ENDPOINT>"
}

Where





 Option 2. Referencing credentials from a Terraform tfvars file 

You can store sensitive information, such as credentials, in a local terraform.tfvars file and reference these credentials in your provider block.
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 1G.

--no-wait, --nw
: Do not wait for the build run to complete. This value is optional. The default value is true.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--runtime-secret, --rs
: The name of the registry secret that is used to authenticate with a private registry to pull a custom runtime. This value is optional.

--runtime-type, --rt
: The type of runtime to use for the function. Valid values are managed and custom. See [Runtime](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-runtime). This value is optional. The default value is managed.

--wait, -w
: Wait for the build run to complete. This value is optional. The default value is true.

--wait-timeout, --wto
: The length of time in seconds to wait for the function to be ready. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 600.





 Example 

ibmcloud ce fn create --name myfunction --build-source main.js --runtime nodejs-18





 Example output 

Preparing function 'myfunction' for build push...
For more information, see [API Endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_api). 



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. For example, you can multiple providers so that you can 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://www.terraform.io/docs/language/providers/configuration.html).



 Option 1. Creating a static provider.tf file 

You can declare the input parameters in the provider block directly.

Because the provider block includes sensitive information, do not commit this file into a public source repository. To add version control to your provider configuration, use a local [terraform.tfvars file](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-terraform-service-keystf-variables).

Create a provider.tf file and specify the input parameters that are required for your resource or data source.

provider "logdna" {
servicekey = "<service_key>"
url = "<API_ENDPOINT>"
}

Where





 Option 2. Referencing credentials from a Terraform tfvars file 

You can store sensitive information, such as credentials, in a local terraform.tfvars file and reference these credentials in your provider block.
* [ibmcloud ce domainmapping delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-domainmapping-delete)
* [ibmcloud ce domainmapping get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-domainmapping-get)
* [ibmcloud ce domainmapping list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-domainmapping-list)
* [ibmcloud ce domainmapping update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-domainmapping-update)



* [Function commands](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function)



* [ibmcloud ce function bind](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-bind)
* [ibmcloud ce function create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-create)
* [ibmcloud ce function delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-delete)
* [ibmcloud ce function get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-get)
* [ibmcloud ce function list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-list)
* [ibmcloud ce function runtimes](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-runtimes)
For more information, see [API Endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_api). 



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. For example, you can multiple providers so that you can 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://www.terraform.io/docs/language/providers/configuration.html).



 Option 1. Creating a static provider.tf file 

You can declare the input parameters in the provider block directly.

Because the provider block includes sensitive information, do not commit this file into a public source repository. To add version control to your provider configuration, use a local [terraform.tfvars file](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-terraform-categoriestf-variables).

Create a provider.tf file and specify the input parameters that are required for your resource or data source.

provider "logdna" {
servicekey = "<service_key>"
url = "<API_ENDPOINT>"
}

Where





 Option 2. Referencing credentials from a Terraform tfvars file 

You can store sensitive information, such as credentials, in a local terraform.tfvars file and reference these credentials in your provider block.

Do not commit the terraform.tfvars into a public source repository.
Valid values are true or false.

--color
: Enable or disable color output. This option is disabled by default. Valid values are true or false.

--http-timeout
: 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.
For more information, see [API Endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_api). 



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. For example, you can multiple providers so that you can 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://www.terraform.io/docs/language/providers/configuration.html).



 Option 1. Creating a static provider.tf file 

You can declare the input parameters in the provider block directly.

Because the provider block includes sensitive information, do not commit this file into a public source repository. To add version control to your provider configuration, use a local [terraform.tfvars file](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-terraform-categoriestf-variables).

Create a provider.tf file and specify the input parameters that are required for your resource or data source.

provider "logdna" {
servicekey = "<service_key>"
url = "<API_ENDPOINT>"
}

Where





 Option 2. Referencing credentials from a Terraform tfvars file 

You can store sensitive information, such as credentials, in a local terraform.tfvars file and reference these credentials in your provider block.

Do not commit the terraform.tfvars into a public source repository.
"website_push_id":"test",
"website_url":"https://test.com",
"pre_prod" : "true" // Set to true in case of configuring Destination as pre-prod Destination (pre_prod destination can only be configured for Standard plan)
}
}
* The following example shows format of the DestinationConfig object for MS Teams destination.

{
"params" : {
"url" : "https://xyz.webhook.office.com"
}
}
* The following example shows format of the DestinationConfig object for IBM Cloud® Functions destination.

{
"params" : {
"url" : "https://www.ibmcfendpoint.com",
"api_key" : "cffunctionnamespaceserviceidapikey"
}
}
* The following example shows format of the DestinationConfig object for PagerDuty destination.

{
"params" : {
"routing_key" : "routingkeytoconnecttoPD",
"api_key" : "cffunctionnamespaceserviceidapikey"
}
}
* The following example shows the format of the DestinationConfig object for webhook.

{
"params" : {
"url" : "exampleString",
"verb" : "get",
"custom_headers" : { },
"sensitive_headers" : [ "exampleString" ]
}
}
* The following example shows the format of the DestinationConfig object for push_android destination.

{
"params" : {
"project_id" : "6232305230320",
"private_key" : "36e21epfweort823or8rt832pr8p2r832pr82pr382r8f",
"client_email" : "testuser.123@gmail.com",
private.jp-tok.kms.cloud.ibm.com crn:v1:bluemix:public:kms:jp-tok:::endpoint:private.jp-tok.kms.cloud.ibm.com 
 Sydney 
 private.us-south.kms.cloud.ibm.com crn:v1:bluemix:public:kms:us-south:::endpoint:private.us-south.kms.cloud.ibm.com 
 private.us-east.kms.cloud.ibm.com crn:v1:bluemix:public:kms:us-east:::endpoint:private.us-east.kms.cloud.ibm.com 
 private.eu-gb.kms.cloud.ibm.com crn:v1:bluemix:public:kms:eu-gb:::endpoint:private.eu-gb.kms.cloud.ibm.com 
 private.eu-de.kms.cloud.ibm.com crn:v1:bluemix:public:kms:eu-de:::endpoint:private.eu-de.kms.cloud.ibm.com 
 private.au-syd.kms.cloud.ibm.com crn:v1:bluemix:public:kms:au-syd:::endpoint:private.au-syd.kms.cloud.ibm.com 
 private.jp-tok.kms.cloud.ibm.com crn:v1:bluemix:public:kms:jp-tok:::endpoint:private.jp-tok.kms.cloud.ibm.com 
 Tokyo 
 private.us-south.kms.cloud.ibm.com crn:v1:bluemix:public:kms:us-south:::endpoint:private.us-south.kms.cloud.ibm.com 
 private.us-east.kms.cloud.ibm.com crn:v1:bluemix:public:kms:us-east:::endpoint:private.us-east.kms.cloud.ibm.com
The plug-in abstracts the IBM Cloud APIs that are used to provision, update, or delete Schematics resources.
2. Create the Terraform configuration files named main.tf, terraform.tfvars, and versions.tf.

You can use the Terraform example Git URL https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-api-gateway. This example uses service instance to set up an API for an IBM Cloud service of your choice. You can specify the API endpoint that you want to use to access your service, and define subscription keys so that you can securely consume your API.

If you have a workspace created other in a region other than us, you must set the API endpoint to that region. For example, if your region specified is eu, the API endpoint should be specified as IBMCLOUD_SCHEMATICS_API_ENDPOINT=https://eu.schematics.cloud.ibm.com in the environment variable. For more information about the Schematics Workspaces locations and endpoints to be used, see [Where is my information stored?](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location).

Then create the Schematics Workspaces tf-testwks-apigwy in the default resource group of your region. This workspace points to a Terraform template of your choice that requires the Terraform version terraform_v1.0.

versions.tf

The sample versions.tf file to specify the provider version that you need to create the workspace.

terraform {
required_version = ">=1.0.0, <2.0"
required_providers {
ibm = {
source = "IBM-Cloud/ibm"
}
}
}

terraform.tfvars

The sample terraform.tfvars file to store sensitive information, such as credentials.
https://myfun.11a66hbi3rhz.us-south.codeengine.appdomain.cloud

Notice the output of the function create command provides information on the progression of the build run before the function is created.

In this example, the built code bundle is uploaded to the ce--abcde-4svg40kna19 namespace in Container Registry.

The following table summarizes the options that are used with the function create command in this example. For more information about the command and its options, see the [ibmcloud ce function create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-create) command.



Table 1. Command description

 Option Description 

 --name The name of the function. Use a name that is unique within the project. This value is required.<br><br><br><br> * The name must begin with a lowercase letter.<br> * The name must end with a lowercase alphanumeric character.<br> * The name must be 63 characters or fewer and can contain letters, numbers, and hyphens (-).<br><br><br> 
 --build-source The URL of the Git repository that contains your source code; for example, https://github.com/IBM/CodeEngine. 
 --build-context-dir The directory in the repository that contains the buildpacks file or the Dockerfile. This value is optional. 
 --runtime The runtime for the function. 



The following output shows the result of the function get command for this example, including information about the build.

Example output

Getting function 'kerstenrepofunction'...
OK

Name: myfun
Project Name: sample
Project ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Age: 27m
Created: 2023-06-27T21:07:26Z
ibmcloud fn deploy -m openwhisk-sdk/packages/tone-analyzer-v3/manifest.yaml
3. Verify that the package is added to your package list.

ibmcloud fn package list

Example output

packages
/myOrg_mySpace/tone-analyzer-v3 private
4. Bind the credentials from the Tone Analyzer instance you created to the package.

ibmcloud fn service bind tone_analyzer tone-analyzer-v3

Depending on the region where you created the service instance, the service instance might be named differently because it is an IAM service. If the command fails, use the following service name for the bind command:

ibmcloud fn service bind tone-analyzer tone-analyzer-v3

Example output

Credentials 'Credentials-1' from 'tone_analyzer' service instance 'Watson Tone Analyzer' bound to 'tone-analyzer-v3'.
5. Verify that the package is configured with your Tone Analyzer service instance credentials.

ibmcloud fn package get tone-analyzer-v3 parameters

Example output

ok: got package tone-analyzer-v3, displaying field parameters
[
{
"key": "__bx_creds",
"value": {
"tone_analyzer": {
"credentials": "Credentials-1",
"instance": "Watson Tone Analyzer",
"password": "AAAA0AAAAAAA",
"url": "https://gateway.watsonplatform.net/assistant/api",
"username": "00a0aa00-0a0a-12aa-1234-a1a2a3a456a7"
}
}
}
]







 Installing from the Cloud Functions console 

Install the Tone Analyzer package from the console.



1. In the Cloud Functions console, go to the [Create page](https://cloud.ibm.com/functions/create).
2.