vania-janet/multiturn-rag-retrieval-data huggingface dataset:
widget0-application1 r006-287258c6-2eb3-4908-b326-6f03c3e47aa6 vpc crn:v1:bluemix:public:is:us-south:a/713c783d9a507a53135fe6793c37cc74::vpc:r006-287258c6-2eb3-4908-b326-6f03c3e47aa6 ACTIVE
widget0-application2 r006-fa51e99e-bd93-4451-a4eb-76eed9939d3c vpc crn:v1:bluemix:public:is:us-south:a/713c783d9a507a53135fe6793c37cc74::vpc:r006-fa51e99e-bd93-4451-a4eb-76eed9939d3c ACTIVE
8. Optionally, navigate to the [resource list](https://cloud.ibm.com/resources) and find the DNS Services, click on it and investigate.







 Step 4: Create the shared microservice and associated DNS record (Shared Team) 



1. Change directory, generate an API key in the local.env and become a member of the shared access group:

team=shared
cd ../$team
echo export TF_VAR_ibmcloud_api_key=$(ibmcloud iam service-api-key-create $team $basename-$team --output json | jq .apikey) > local.env
cat local.env
source local.env
2. Optionally, dig deeper at this point into some of the Terraform source code. The shared team is going to provide microservices. Although the network team has already created the shared VPC and some network resources the shared team will create the instance and choose the instance profile.
name = "widgets.example.com"
instance_id = ibm_resource_instance.dns.guid
description = "this is a description"
label = "this-is-a-label"
}

The zone is then added to a VPC as a permitted network:

resource "ibm_dns_permitted_network" "shared" {
instance_id = ibm_resource_instance.dns.guid
zone_id = ibm_dns_zone.widgets_example_com.zone_id
vpc_crn = module.vpc_shared.vpc.crn
type = "vpc"
}
7. List the DNS configuration. A DNS Services instance was created. The widgets.example.com zone was created. Finally, the zone was added to all the VPCs.

ibmcloud dns instances

ibmcloud dns zones -i $basename-dns

zone_id=$(ibmcloud dns zones -i $basename-dns --output json | jq -r '.[] | .id')
ibmcloud dns permitted-networks $zone_id -i $basename-dns

The output will resemble this:

$ ibmcloud dns instances
Retrieving service instances for service 'dns-svcs' ...
OK
Name ID Location State Service Name
widget0-dns 3b0d5546-5999-4c7e-a757-f5fd21dd44ed global active dns-svcs
$ ibmcloud dns zones -i $basename-dns
Listing zones for service instance 'widget0-dns' ...
OK
ID Name Status
5a1a2295-1c38-49dd-9809-aaaf5a127e79c1b widgets.example.com ACTIVE
$ zone_id=$(ibmcloud dns zones -i $basename-dns --output json | jq -r '.[] | .id')
You must complete configuration for the draft environment before you can add the extension in the live environment.
3. In the Connect step, click the link to log in to your Segment account in another browser tab.

If you do not already have a Segment account, click Sign up for free account to create one. Verify your email address and complete your profile to activate your account.
4. In the Segment web app, go to your workspace. In the Sources section, find the Add IBM Watson Assistant Source tile and click Add Source.
5. In the Source Name field, type a descriptive name for your Watson Assistant instance (for example, Customer Care Assistant). Click Create Source.
6. Click Copy to copy the generated key to the clipboard.
7. Go back to the Segment integration settings in the Watson Assistant interface. In the Segment key field, paste the key you copied from the Segment web app in the previous step. Click Next.
8. In the Select events step, review the list of events Watson Assistant can send to Segment.

Each row in the table shows the name of a supported event, along with a brief description.
9. Click the checkboxes to select the events you want to send to Segment. Click Next.
10. In the Review & Confirm step, review the configuration and click Finish.



The Segment extension is now connected to your assistant in the draft environment. Click Close to close the integration settings.





 Configuring the extension for the live environment 

To configure the Segment extension for the live environment, follow these steps:



1. On the ![Integrations icon](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/integrations-icon.png)Integrations page, scroll to the Extensions section and find the tile for the Segment extension.
2. Click Open. The Open extension window opens.
3. In the Environment field, select Live. Click Confirm.
4.
* UI
* CLI
* API
* Terraform







 Adding a connection 

You can add a connection to a transit gateway using the UI, CLI, and API.



 Adding a connection in the UI 

To add a connection to a transit gateway, follow these steps:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2. Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) from the upper left, then click Interconnectivity.
3. Click Transit Gateway from the left navigation pane.
4. Click the name of the transit gateway where you want to add a connection.

If you are in the expanded view, click View details.
5. Click Add connection.
6. Choose and configure the specific network connections that you want to add to your transit gateway. Choices include:



* Classic infrastructure - Allows you to connect to IBM Cloud classic resources.
* VPC - Allows you to connect to your account's VPC resources, or VPC resources from other accounts as well.
* Unbound GRE tunnel - Allows a transit gateway to connect to overlay networks hosted on classic infrastructure resources. For prerequisites and detailed instructions, see [Creating an Unbound Generic Routing Encapsulation tunnel connection](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-unbound-gre-connection).
* Direct Link - Creates a network connection to and from Direct Link 2.0 gateways so that there is a secure connection to on-premises networks and other resources connected to the transit gateway.

If you select Direct Link, you must also log in to the [Direct Link console](https://cloud.ibm.com/interconnectivity/direct-link) (using the same IBM Cloud account) and specify Transit Gateway as the type of network connection for your direct link.



7. Click Add to create a connection.
* UI
* CLI
* API
* Terraform







 Editing a connection 



 Editing a connection in the UI 

To edit a connection to a transit gateway, follow these steps:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2. Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) from the upper left, then click Interconnectivity.
3. Click Transit Gateway from the left navigation pane.
4. Click the name of the transit gateway where you want to edit a connection.

If you are in the expanded view, click View details.
5. From the Connections page, click the Actions menu ![Actions menu](https://cloud.ibm.com/docs-content/v1/content/6a28e4ae2660b609a18e90e1239ed772f80373d6/transit-gateway//images/overflow.png) next to the connection that you want to edit and select Edit.

From here, you can change the name of the selected network connection.







 Editing a connection from the CLI 

To edit a connection from the CLI, execute this command:

ibmcloud tg connection-update|cu GATEWAY_ID CONNECTION_ID --name NAME [--output json] [-h, --help]

Where:



* GATEWAY_ID: ID of the gateway the connection being updated is on.
* CONNECTION_ID: ID of the connection to update.
* --name: New name of the connection.
* --output json: Optional: Specify if you want the output displayed in JSON format.
* --help | -h: Optional: Get help on this command.





 Example 

This example illustrates updating the name of a connection to MyConn2:

ibmcloud tg cu $gateway $connection --name MyConn2







 Editing a connection with the API
widget0-shared AccessGroupId-30d73f44-5602-47a7-846e-e6480c9dceff shared administrators
$ ibmcloud iam service-ids | grep $basename
ServiceId-5e919b97-380c-4343-a337-3901cafbd956 widget0-application2 2020-07-15T21:25+0000 2020-07-15T22:03+0000 application 2 service id false
ServiceId-307df062-f4b7-45f8-8ec8-94ad1ed61730 widget0-network 2020-07-15T21:49+0000 2020-07-15T22:03+0000 network service id false
$ ibmcloud iam access-group-policies $basename-network
Retrieving all policies of access group widget0-network under account 8675309 as jenny@example.com
OK

Policy ID: 00ceb354-7360-4ad5-9fda-5c03e462c5c0
Roles: Editor
Resources:
Resource Group ID 91518c45e47a427fa4f63edb58e4f227
Resource Group Name widget0-shared
Service Name is
flowLogCollectorId 
Memo Policy applies to the resource(s) within the resource group

Policy ID: 115ebe9f-eea0-4308-9e7f-bb887d64426b
Roles: Editor
Resources:
Resource Group ID db2f3dc8aacf4a6aa2d2fa07e795cb57
Resource Group Name widget0-application1
Service Name is
vpnGatewayId 
Memo Policy applies to the resource(s) within the resource group
...
5. Optionally navigate to the account [Resource groups](https://cloud.ibm.com/account/resource-groups) and find the resource groups.
6.
![explore-weatherapp-3.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/explore-weatherapp-3.png)



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





 Add a new OpenAPI spec and invoke an existing REST service 



1. Launch the API Designer. In your terminal, enter apic edit.
2. Log in using your IBMid. ![screenshot_apic-edit_login.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/screenshot_apic-edit_login.png)
3. In the API Designer, ensure that the navigation panel is open. If not, click >> to open it. In the API Designer navigation panel, select Drafts > APIs.
4. In the APIs panel, select Add > New API.
5. In the New API window, enter "Weather Provider API" for the title. The Name and Base Path are auto-populated.
![toolkit-add-new-api.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/toolkit-add-new-api.png)
6. Click Create API to complete the wizard.
7. After your API is created, the Design tab is selected.
8. Scroll to the Host panel. Enter $(catalog.host) as the value if the field is not automatically completed.
9.
3. spoke <-> spoke
4. enterprise <--transit firewall-router--> spoke



This routing can be achieved by adding these routes to the transit ingress route table:



 Zone Destination Next hop 

 Dallas 1 10.1.0.0/24 Delegate 
 Dallas 2 10.2.0.0/24 Delegate 
 Dallas 3 10.3.0.0/24 Delegate 





1. To observe the current value of the ingress route table visit the [Routing tables for VPC](https://cloud.ibm.com/vpc-ext/network/routingTables) in the IBM Cloud console. Select the transit VPC from the drop down and then select the tgw-ingress routing table.
2. Make the changes to the routing table by applying the transit_ingress layer:



./apply.sh transit_ingress_tf



1. Refresh the browser display of the routing table to observe the new routes.
2. Run the test suite.

Your expected results are: All tests will result in PASSED with the exception of enterprise <-> spoke(s) that are cross zones.

pytest -m "curl and lz1 and (rz1 or rz2)"







 Step 8: Add Spoke Egress routes to fix Asymmetric Routing 

This step will identify and fix a cross zone asymmetric routing issue. The diagram below shows the successful routes in green. Notice the arrow in both directions. One of the unsuccessful routes has an initial route in blue and an unsuccessful return route in red:

Zoom

![Asymmetric traffic needs to be fixed](https://cloud.ibm.com/docs-content/v1/content/6a28e4ae2660b609a18e90e1239ed772f80373d6/transit-gateway/includes/solution-tutorials/includes/solution-tutorials/images/vpc-transit/vpc-transit-asymmetric.svg)

Asymmetric traffic needs to be fixed



 Asymmetric Routing Limitation
deployments.extensions/rollback <br><br> * <br><br><br> create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 deployments.extensions/scale get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 endpoints get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 events get, list, watch get, list, watch get, list, watch 
 horizontalpodautoscalers.autoscaling get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 ingresses.extensions get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 jobs.batch get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch 
 limitranges get, list, watch get, list, watch get, list, watch 
 localsubjectaccessreviews <br><br> * <br><br><br> <br><br> * <br><br><br> create 
 namespaces get, list, watch get, list, watch get, list, watch <br>cluster-admin only: create, delete 
 namespaces/status get, list, watch get, list, watch get, list, watch 
 networkpolicies get, list, watch create, delete, deletecollection, get, list, patch, update, watch create, delete, deletecollection, get, list, patch, update, watch
This documentation is for the classic Watson Assistant experience. To see the documentation for the new Watson Assistant, please go [here](https://cloud.ibm.com/docs/watson-assistant).



 Expressions for accessing objects 

You can write expressions that access objects and properties of objects by using the Spring Expression (SpEL) language. For more information, see [Spring Expression Language (SpEL)](https://docs.spring.io/spring/docs/3.0.x/reference/expressions.html).



 Evaluation syntax 

To expand variable values inside other variables or invoke methods on properties and global objects, use the <? expression ?> expression syntax. For example:



* Expanding a property

"output":{"text":"Your name is <? context.userName ?>"}
* Invoking methods on properties of global objects

"context":{"email": "<? @email.literal ?>"}







 Shorthand syntax 

Learn how to quickly reference the following objects by using the SpEL shorthand syntax:



* [Context variables](https://cloud.ibm.com/docs/assistant?topic=assistant-expression-languageexpression-language-shorthand-context)
* [Entities](https://cloud.ibm.com/docs/assistant?topic=assistant-expression-languageexpression-language-shorthand-entities)
* [Intents](https://cloud.ibm.com/docs/assistant?topic=assistant-expression-languageexpression-language-shorthand-intents)





 Shorthand syntax for context variables 

The following table shows examples of the shorthand syntax that you can use to write context variables in condition expressions.



 Shorthand syntax Full syntax in SpEL 

 $card_type context['card_type'] 
 $(card-type) context['card-type'] 
 $card_type:VISA context['card_type'] == 'VISA' 
 $card_type:(MASTER CARD) context['card_type'] == 'MASTER CARD'
[Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 Extension Service API Definition: Manage ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 Extension Service API Definition: View ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 Extension Services: View !
Speech to Text docs 

Use the IBM Watson Speech to Text service to transcribe spoken audio to written text. The documentation describes the Speech to Text service for IBM Cloud, IBM Cloud Pak for Data, and IBM Cloud Pak for Data as a Service.

  Developer tools 

[API & SDK reference](https://cloud.ibm.com/apidocs/speech-to-text)

  Recommended content 

[About A brief introduction to the service and its capabilities.](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-about)[Service features A more detailed description of the service and its capabilities.](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-service-features)[Getting started with Speech to Text A brief tutorial that demonstrates speech recognition.](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-gettingStarted)[Release notes for IBM Cloud A summary of the latest releases and updates for IBM Watson Speech to Text for IBM Cloud.](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-release-notes)[Release notes for IBM Cloud Pak for Data A summary of the latest releases and updates for IBM Watson Speech to Text for IBM Cloud Pak for Data.](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-release-notes-data)

  Video library 

[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/speech-to-text//images/getting-started-thumbnail.png)<br><br>Getting started with the Speech to Text service for IBM Cloud](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-gettingStarted)
PUT https://{bucket-name}.{endpoint} virtual host style

Example request

This is an example of creating a new bucket called 'secure-files'.

PUT /secure-files HTTP/1.1
Authorization: Bearer {token}
Content-Type: text/plain
Host: s3.us-south.objectstorage.s3.us-south.cloud-object-storage.appdomain.cloud.net
ibm-service-instance-id: {ibm-service-instance-id}
ibm-sse-kp-encryption-algorithm: "AES256"
ibm-sse-kp-customer-root-key-crn: {customer-root-key-id}

Example request

PUT /secure-files HTTP/1.1
Authorization: 'AWS4-HMAC-SHA256 Credential={access-key}/{date}/{region}/s3/aws4_request,SignedHeaders=host;x-amz-date;,Signature={signature}'
x-amz-date: {timestamp}
Content-Type: text/plain
Host: s3.us.cloud-object-storage.appdomain.cloud
ibm-sse-kp-encryption-algorithm: "AES256"
ibm-sse-kp-customer-root-key-crn: {customer-root-key-id}

Example response

HTTP/1.1 200 OK
Date: Wed, 24 Aug 2016 17:45:25 GMT
X-Clv-Request-Id: dca204eb-72b5-4e2a-a142-808d2a5c2a87
Accept-Ranges: bytes
Server: Cleversafe/3.9.0.115
X-Clv-S3-Version: 2.5
x-amz-request-id: dca204eb-72b5-4e2a-a142-808d2a5c2a87
Content-Length: 0
"href": "https://us-south.iaas.cloud.ibm.com/v1/security_groups/b79365be-f626-45d4-94ae-83f16fa4edd3",
"id": "b79365be-f626-45d4-94ae-83f16fa4edd3",
"name": "my-security-group",
"resource_type": "security_group"
}
],
"subnet": {
"crn": "crn:[...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/subnets/c2338e66-dcb5-4e9b-b572-108d47ca479a",
"id": "c2338e66-dcb5-4e9b-b572-108d47ca479a",
"name": "my-subnet",
"resource_type": "subnet"
},
"transit_encryption": "provider_managed",
"virtual_network_interface": {
"crn": "crn:[...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/virtual_network_interfaces/4551a68d-b45d-4443-b6b3-aba7a4a18c98",
"id": "4551a68d-b45d-4443-b6b3-aba7a4a18c98",
"name": "my-virtual-network-interface",
"resource_type": "virtual_network_interface"
},
"vpc": {
"crn": "crn:[...]",
For more information about the Let's Encrypt certificate chain, see [https://letsencrypt.org/certificates/](https://letsencrypt.org/certificates/).

-----BEGIN CERTIFICATE-----
MIIFFjCCAv6gAwIBAgIRAJErCErPDBinU/bWLiWnX1owDQYJKoZIhvcNAQELBQAw
TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh
cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwHhcNMjAwOTA0MDAwMDAw
WhcNMjUwOTE1MTYwMDAwWjAyMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNTGV0J3Mg
RW5jcnlwdDELMAkGA1UEAxMCUjMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC7AhUozPaglNMPEuyNVZLD+ILxmaZ6QoinXSaqtSu5xUyxr45r+XXIo9cP
R5QUVTVXjJ6oojkZ9YI8QqlObvU7wy7bjcCwXPNZOOftz2nwWgsbvsCUJCWH+jdx
sxPnHKzhm+/b5DtFUkWWqcFTzjTIUu61ru2P3mBw4qVUq7ZtDpelQDRrK9O8Zutm
NHz6a4uPVymZ+DAXXbpyb/uBxa3Shlg9F8fnCbvxK/eG3MHacV3URuPMrSXBiLxg
$service'.secret.key": "'$secret_access_key'"
}' --env '{
"COS_PARQUET": "cos://'$bucket'.'$service'/logs-stream-landing/topic=webserver/jobid='$jobid'/"
}'

Check out the platform log and look for something that looks like this:

+---------------------------+-----+--------------------+--------------------+------------+--------------------+
_corrupt_or_schema_mismatchbytes host requestresponseCode time_stamp
+---------------------------+-----+--------------------+--------------------+------------+--------------------+
 null 9867 ntigate.nt.comGET /software/win... 200[ ! ! ! 01/Jul/1995:04:1...
 null 7634piweba3y.prodigy.comGET /shuttle/miss... 20001/Jul/1995:04:1...
 null25218 ntigate.nt.comGET /software/win... 20001/Jul/1995:04:1...
 null 4441 ntigate.nt.comGET /software/win... 20001/Jul/1995:04:1...
"not_after": "2021-06-04T15:25:44Z",
"not_before": "2021-06-03T15:25:44Z"
},
"versions": [
{
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2021-06-03T20:50:11.278296706Z",
"expiration_date": "2021-06-04T15:25:44Z",
"id": "be4a0846-4cb5-3bfa-bab5-10a44dfc3e85",
"serial_number": "fc:22:29:7e:57:25:8a:05",
"validity": {
"not_after": "2021-06-04T15:25:44Z",
"not_before": "2021-06-03T15:25:44Z"
}
}
]
},
"wrap_info": null,
"warnings": null,
"auth": null
}

A request to import a certificate to an existing secret group returns the following response:

{
"request_id": "811b893b-55c7-b6bb-4e55-26a7a8362164",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"algorithm": "RSA",
"common_name": "example.com",
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2021-06-03T20:50:11Z",
Enabling SSL verification is highly recommended. Disabling SSL jeopardizes the security of the connection and data. Disable SSL only if necessary and only with data that is not confidential, and take steps to enable SSL as soon as possible.





 Example curl requests 

The following examples demonstrate the use of curl. The requests use the Speech to Text service to transcribe audio to text with both IBM Cloud® and IBM Cloud Pak® for Data.

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/flac" --data-binary ./audio-file.flac "{url}/v1/recognize"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: audio/flac" --data-binary ./audio-file.flac "{url}/v1/recognize"

In both examples, you replace {url} with the URL for your service instance. Authentication differs between IBM Cloud®, where you replace {apikey} with the API key for your service instance, and IBM Cloud Pak® for Data, where you replace {token} with an access token that you generate for your service instance. For more information about authenticating to the service on either platform, see [Authenticating to Watson services](https://cloud.ibm.com/docs/watson?topic=watson-iam).

When submitting requests based on examples in the documentation, omit the braces ({ }) from the examples; they indicate variable values that you must replace with actual values. Windows users must replace the backslash () at the end of each line with a caret (^). Make sure there are no trailing spaces after a or ^.