vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Type: The type of information to be evaluated by the rule: the name of the host from which the request originated, an HTTP header field, or a path in the URL.
* Value: The value to be matched.
* Key: The name of the HTTP header field to evaluate, if the rule type is Header. For example, to match a cookie in the HTTP header, enter Cookie for the key.











 Creating an application load balancer from the CLI 

The following example illustrates using the CLI to create an Application Load Balancer for VPC (ALB). In this example, it is in front of one VPC virtual server instance (ID 0716_6acdd058-4607-4463-af08-d4999d983945) running a TCP server that listens on port 9090. The load balancer has a front-end listener, which allows secure access to the TCP server.

To create an application load balancer by using the CLI, follow these steps:



1. Set up your [CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).
2. Use the terminal to log in to your account using the CLI. After you enter the password, the system prompts which account and region you want to use:

ibmcloud login --sso
3. Create a load balancer:

ibmcloud is load-balancer-create alb-test public --subnet 0896-b1f24514-89dc-4afd-b0e2-5489a43cf45c --family application

Sample output:

Creating load balancer nlb-test in resource group under account IBM Cloud Network Services as user test@ibm.com...

ID r134-99b5ab45-6357-42db-8b32-5d2c8aa62776
Name alb-test
[From the Locations console](https://cloud.ibm.com/satellite/locations), select the location where you want to create a storage configuration.
2. Select Storage > Create storage configuration
3. Enter a name for your configuration.
4. Select the Storage type.
5. Select the Version and click Next
6. If the Storage type that you selected accepts custom parameters, enter them on the Parameters tab.
7. If the Storage type that you selected requires secrets, enter them on the Secrets tab.
8. On the Storage classes tab, review the storage classes that are deployed by the configuration or create a custom storage class.
9. On the Assign to service tab, select the service that you want to assign your configuration to.
10. Click Complete to assign your storage configuration.







 Creating a configuration in the CLI 



1. Log in to the IBM Cloud CLI.

ibmcloud login
2. List your Satellite locations and note the Managed from column.

ibmcloud sat location ls
3. Target the Managed from region of your Satellite location. For example, for wdc target us-east. For more information, see [Satellite regions](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-regions).

ibmcloud target -r us-east
4. If you use a resource group other than default, target it.

ibmcloud target -g <resource-group>
5. Copy one of the following example command for the template version that you want to use. For more information about the command, see ibmcloud sat storage config create in the [command reference](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-storage-config-create).

Example command to create a version 1.4.0 configuration.
For more information, see [Protecting Cloud Databases resources](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-cbrcbr-overview-protect-services).
7. Click Continue.
8. Define the allowed endpoint types.



* Keep the toggle set to No to allow all endpoint types.
* Set the toggle to Yes to allow only specific endpoint types, then choose from the list.



9. Select a network zone or zones that you have already created, or create a new network zone by clicking Create.

Contexts define from where your resources can be accessed, effectively linking your network zone to your rule.
10. Click Add to add your configuration to the summary.
11. Click Next.
12. Name your rule.
13. Select how you want to enforce the rule.

Report-only is not available for Cloud Databases.







 Creating rules in the CLI 

To create rules in the CLI, [install the context-based restrictions CLI plug-in](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugininstall-cbr-plugin).

To create a rule in the CLI, you need the appropriate Cloud Databases service_name:



* databases-for-etcd
* databases-for-elasticsearch
* databases-for-mongodb
* databases-for-postgresql
* databases-for-redis
* messages-for-rabbitmq
* databases-for-cassandra
* databases-for-enterprisedb
* database-for-mysql



Create a rule by using a command like:
"secret_type": "private_cert",
"server_flag": true,
"street_address": [],
"ttl_seconds": 43200,
"updated_at": "2022-10-05T21:33:11Z",
"use_csr_common_name": true,
"use_csr_sans": true
}





 Adding a certificate template from the CLI 

You can create a certificate template for your service instance by using the Secrets Manager CLI.

The following example shows a command that you can use to create a certificate template and associate it with an existing intermediate certificate authority that is configured for your instance.

ibmcloud secrets-manager configuration-create
--configuration-prototype='{
"config_type": "private_cert_configuration_template",
"name": "example-certificate-template",
"allow_any_name": true,
"allow_bare_domains": true,
"allow_glob_domains": true,
"allow_ip_sans": true,
"allow_localhost": true,
"allow_subdomains": false,
"allow_wildcard_certificates": true,
"allowed_domains": ["example.com","acme.com"],
"allowed_domains_template": true,
"allowed_other_sans": [
"1.2.3.5.4.3.201.10.4.3;utf8:test@example.com",
"1.3.6.1.4.1.201.10.5.5;UTF-8:"
],
"allowed_secret_groups": "d898bb90-82f6-4d61-b5cc-b079b66cfa76",
"allowed_uri_sans": ["example.com","acme://"],
"certificate_authority": "example-intermediate-CA",
[From the Locations console](https://cloud.ibm.com/satellite/locations), select the location where you want to create a storage configuration.
2. Select Storage > Create storage configuration
3. Enter a name for your configuration.
4. Select the Storage type.
5. Select the Version and click Next
6. If the Storage type that you selected accepts custom parameters, enter them on the Parameters tab.
7. If the Storage type that you selected requires secrets, enter them on the Secrets tab.
8. On the Storage classes tab, review the storage classes that are deployed by the configuration or create a custom storage class.
9. On the Assign to service tab, select the service that you want to assign your configuration to.
10. Click Complete to assign your storage configuration.







 Creating a configuration in the CLI 



1. Log in to the IBM Cloud CLI.

ibmcloud login
2. List your Satellite locations and note the Managed from column.

ibmcloud sat location ls
3. Target the Managed from region of your Satellite location. For example, for wdc target us-east. For more information, see [Satellite regions](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-regions).

ibmcloud target -r us-east
4. If you use a resource group other than default, target it.

ibmcloud target -g <resource-group>
5. Copy one of the following example command for the template version that you want to use. For more information about the command, see ibmcloud sat storage config create in the [command reference](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-storage-config-create).

Example command to create a version 2.2 configuration.
[From the Locations console](https://cloud.ibm.com/satellite/locations), select the location where you want to create a storage configuration.
2. Select Storage > Create storage configuration
3. Enter a name for your configuration.
4. Select the Storage type.
5. Select the Version and click Next
6. If the Storage type that you selected accepts custom parameters, enter them on the Parameters tab.
7. If the Storage type that you selected requires secrets, enter them on the Secrets tab.
8. On the Storage classes tab, review the storage classes that are deployed by the configuration or create a custom storage class.
9. On the Assign to service tab, select the service that you want to assign your configuration to.
10. Click Complete to assign your storage configuration.







 Creating a configuration in the CLI 



1. Log in to the IBM Cloud CLI.

ibmcloud login
2. List your Satellite locations and note the Managed from column.

ibmcloud sat location ls
3. Target the Managed from region of your Satellite location. For example, for wdc target us-east. For more information, see [Satellite regions](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-regions).

ibmcloud target -r us-east
4. If you use a resource group other than default, target it.

ibmcloud target -g <resource-group>
5. Copy one of the following example command for the template version that you want to use. For more information about the command, see ibmcloud sat storage config create in the [command reference](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-storage-config-create).

Example command to create a version 2.5.1 configuration.
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:
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==





 7. Your simple contract is ready 

env: 
type: env
logging:
logDNA:
hostname: syslog-a.au-syd.logging.cloud.ibm.com
ingestionKey: xxxxxxxxxx
port: 6514
workload: 
type: workload
compose:
type String The response type:<br><br><br><br> * text_to_speech: a command to play an utterance to the caller<br> * sms: a command to send an SMS message to the caller<br> * url: a command to play an audio file to the caller<br> * transfer: a command to transfer a call<br> * text_to_speech_config: a command to change the Text to Speech settings<br> * speech_to_text_config: a command to change the Speech to Text settings<br> * pause_speech_to_text: a command to stop speech recognition<br> * unpause_speech_to_text: a command to start speech recognition<br> * pause_dtmf: a command to stop processing of inbound DTMF signals<br> * unpause_dtmf: unpause_dtmf: a command to start processing of inbound DTMF signals<br> * enable_speech_barge_in: a command to enable speech barge-in so that callers can interrupt playback by speaking<br> * disable_speech_barge_in: a command to disable speech barge-in so that playback isn't interrupted when callers speak during audio playback<br> * enable_dtmf_barge_in: a command to enable DTMF barge-in so that callers can interrupt playback from the phone integration by pressing a key<br> * disable_dtmf_barge_in: a command to disable DTMF barge-in so that playback from the phone integration isn't interrupted when the caller presses a key<br> * dtmf: a command to send DTMF signals to the caller<br> * hangup: a command to disconnect the call <br> See [Mapping between CDR and Watson Assistant response types](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-cdr-log-referencecdr-log-reference-response-type-mapping).<br><br><br> 
 barge_in_occurred Boolean Whether barge-in occurred during the turn. 
 streaming_statistics Object Information and statistics related to Text to Speech synthesis and playback.
To update output.generic using the JSON editor, see [Defining responses using the JSON editor](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-responses-json)).



 Text 

The text response type is used for ordinary text responses from the dialog:

{
"output": {
"generic":[
{
"response_type": "text",
"text": "OK, you want to fly to Boston next Monday."
}
]
},
"user_id": "faf4a112-f09f-4a95-a0be-43c496e6ac9a"
}

Note that for backward compatibility, the same text is also included in the output.text array in the dialog response (as shown in the example at the beginning of this page).





 Image 

The image response type instructs the client application to display an image, optionally accompanied by a title and description:

{
"output": {
"generic":[
{
"response_type": "image",
"source": "http://example.com/image.jpg",
"title": "Image example",
"description": "This is an example image"
}
]
},
"user_id": "faf4a112-f09f-4a95-a0be-43c496e6ac9a"
}

Your application is responsible for retrieving the image specified by the source property and displaying it to the user. If the optional title and description are provided, your application can display them in whatever way is appropriate (for example, rendering the title after the image and the description as hover text).





 Video 

The video response type instructs the client application to display a video, optionally accompanied by a title, description and alt_text for accessibility:

{
"output": {
"generic":[
{
"response_type": "video",
: If you use the CLI, you can specify the --api-types option and the crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster type.
: If you use the API, you can specify "api_type_id": "crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster" in the "operations" spec.

Management APIs
: Protect access to the APIs for provisioning and managing clusters, worker pools, and more. CBR rules that apply to the management API type control access the IBM Cloud Kubernetes Service APIs, which includes all ibmcloud ks commands calls, such as ibmcloud ks clusters, ibmcloud ks cluster create, and more. If you select the management APIs in your CBR rule, then resources in the network zone that associate with the rule can interact with the management APIs.
: If you use the CLI, you can specify the --api-types option and the crn:v1:bluemix:public:containers-kubernetes::::api-type:management type.
: If you use the API, you can specify "api_type_id": "crn:v1:bluemix:public:containers-kubernetes::::api-type:management" in the "operations" spec.

To follow an example CBR scenario, see [Setting up context-based restrictions](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorial).





 Allowing IBM Cloud Kubernetes Service to access other IBM Cloud resources by using CBR 

You must add the containers-kubernetes to your network zones for rules created against the following services.

IAM Identity service
: Allow IBM Cloud Kubernetes Service to create tokens and API Keys like the cluster API Key and the IBM Cloud Container Registry token and API Key.

IAM Access Management Service
: Allow IBM Cloud Kubernetes Service to create an IAM Access Policy for Reader service access role to IBM Cloud Container Registry.

IAM Access Groups Service
Click Create.

Instead of creating a zone by using UI inputs, you can use the JSON code form to directly enter JSON to create a zone by clicking Enter as JSON code.
3. Enter a unique name and a description.
4. Enter the allowed IP addresses where an access request can originate. Include IP address exceptions in the deny list, if necessary.
5. Enter the allowed VPCs.

If you want to allow access from the VPC to public endpoints in your rule, include any public gateway IP addresses in the zone definition along with the VPC.
6. Reference a service. Select the service type and then select a service. Click Add to associate the service's IP addresses with your network zone.

If you're not sure what the service type is, view the table [Services integrated with context-based restrictions](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-whatiscbr-adopters).
7. Click Next to review your network zone.
8. Click Create.



You can continue by creating more network zones, or by creating rules.





 Creating network zones by using the CLI 

By creating network zones, you establish a list of allowed locations where an access request originates. A set of one or more network locations can be specified by IP addresses such as individual addresses, ranges or subnets, and VPC IDs. After you create a network zone, you can add it to a rule.



1. Install the [Context-based restrictions CLI plug-in](https://cloud.ibm.com/docs/account?topic=account-cbr-plugin) by running the following command:

ibmcloud plugin install cbr
2. To create a network zone, use the [cbr zone-create](https://cloud.ibm.com/docs/account?topic=account-cbr-plugincbr-cli-zone-create-command) command.

The following example creates a network zone with a list of allowed network locations.
Type '4' and press enter.

===============================================================================
Select a language:

1. Go
2. Java - MicroProfile / Java EE
3. Java - Spring
4. Node
5. Python - Django
6. Python - Flask
7. Swift
-------------------------
0. Return to the previous selection

===============================================================================
? Enter selection number:> 4

After you make your selection for the programming language and framework, the next selection will have so many options, it might scroll past your wanted service. As you can see in the example, we wish to use a simple Node.js Web App with Express.js. Type '3' and press enter.

===============================================================================
Select a Starter Kit:

APPSERVICE
* billingType: Enter the billing type that you want to use for your PVCs. Choose between hourly or monthly. If you don't specify this label, all PVCs are created with an hourly billing type.



labels
: In the spec template metadata section, enter the same labels that you added to the spec.selector.matchLabels section.

affinity
: In the spec template spec affinity section, specify your anti-affinity rule to ensure that your stateful set pods are distributed across worker nodes and zones. The example shows an anti-affinity rule where the stateful set pod prefers not to be scheduled on a worker node where a pod runs that has the app: nginx label. The topologykey: failure-domain.beta.kubernetes.io/zone restricts this anti-affinity rule even more and prevents the pod to be scheduled on a worker node if the worker node is in the same zone as a pod that has the app: nginx label. By using this anti-affinity rule, you can achieve anti-affinity across worker nodes and zones.

name
: In the spec volume claim templates metadata section, enter a name for your volume. Use the same name that you defined in the spec.containers.volumeMount.name section. The name that you enter here is used to create the name for your PVC in the format: <volume_name>-<statefulset_name>-<replica_number>.

storage
: In the spec volume claim templates spec resources requests section, enter the size of the File Storage for Classic in gigabytes (Gi).

iops
: In the spec volume claim templates spec resources requests section, if you want to provision [performance storage](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_predefined_storageclass), enter the number of IOPS. If you use an endurance storage class and specify a number of IOPS, the number of IOPS is ignored. Instead, the IOPS that is specified in your storage class is used.

storageClassName
: In the spec volume claim templates spec section, enter the storage class that you want to use.
[Conditions](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/action-conditions-editor.png)

Conditions
6. To add more than one condition to an action, click Add condition.
7. To add another group of conditions, click New condition group.

You can use groups to build complex action conditions. Each group is evaluated true or false as a whole, and then these results are evaluated together. For example, you might build an action that executes only if all conditions in group 1 are true or any condition in group 2 is true. (Groups function like parentheses in the boolean conditions of many programming languages.)

After you add a group, you can define one or more conditions in the new group. Between groups, choose and or or to indicate whether the conditions in both conditional groups or only one of them must be met for the step to be included in the conversational flow.





 Operators 

An operator specifies the kind of test you are performing on a value in a condition. The specific operators available in a condition depend on the customer response type of the value, as shown in the following table.



Operators

 Response type Operators 

 <br><br> * Options<br><br><br> <br><br> * is<br> * is not<br> * is any of<br> * is none of<br><br><br> 
 <br><br> * Regex<br><br><br> <br><br> * is<br> * is not<br><br><br>
* billingType: Enter the billing type that you want to use for your PVCs. Choose between hourly or monthly. If you don't specify this label, all PVCs are created with an hourly billing type.



labels
: In the spec template metadata section, enter the same labels that you added to the spec.selector.matchLabels section.

affinity
: In the spec template spec affinity section, specify your anti-affinity rule to ensure that your stateful set pods are distributed across worker nodes and zones. The example shows an anti-affinity rule where the stateful set pod prefers not to be scheduled on a worker node where a pod runs that has the app: nginx label. The topologykey: failure-domain.beta.kubernetes.io/zone restricts this anti-affinity rule even more and prevents the pod to be scheduled on a worker node if the worker node is in the same zone as a pod that has the app: nginx label. By using this anti-affinity rule, you can achieve anti-affinity across worker nodes and zones.

name
: In the spec volume claim templates metadata section, enter a name for your volume. Use the same name that you defined in the spec.containers.volumeMount.name section. The name that you enter here is used to create the name for your PVC in the format: <volume_name>-<statefulset_name>-<replica_number>.

storage
: In the spec volume claim templates spec resources requests section, enter the size of the File Storage for Classic in gigabytes (Gi).

iops
: In the spec volume claim templates spec resources requests section, if you want to provision [performance storage](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_predefined_storageclass), enter the number of IOPS. If you use an endurance storage class and specify a number of IOPS, the number of IOPS is ignored. Instead, the IOPS that is specified in your storage class is used.

storageClassName
: In the spec volume claim templates spec section, enter the storage class that you want to use.