vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* App name: The name of the app. The default app name is the same as your toolchain name.
* IBM Cloud API Key: The API key that is used to interact with the ibmcloud CLI tool in several tasks. Use one of the following methods to specify the API key that you want to use:



* Click the key icon to import an existing API key from a secrets vault of your choice.
* Copy and paste an existing API key.
* Click New to create an API key.
* Generate a new api-key if you don’t have an existing API key.



You can immediately save the generated API key to an existing secrets vault of your choice.
* Container registry region: The Container Registry region in which your container namespace is located.
* Container registry namespace: Select from the list of container namespaces in the associated Container Registry region.
* Code Engine region: The region in which your Code Engine project is located.
* Code Engine Resource Group: The Resource Group where your Code Engine project was created.
* Code Engine project: The name of the project that was created in Code Engine. Your app is deployed to this project.



Zoom

![Code Engine secure app deployment target details for Rolling or Blue-Green](https://cloud.ibm.com/docs-content/v1/content/efbf7b33e3aca029f69f9244bced9dd4d8acb848/apps/includes/ContinuousDelivery/includes/ContinuousDelivery/images/code_engine_dep_target.png)

Figure 5. Code Engine secure app rolling deployment target details
2. Click Continue.







 Step 3: Add optional tool integrations 

You can add the IBM Cloud® DevOps Insights tool integration to your toolchain without any additional configuration.

[DevOps Insights](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-di_working) is included in the created toolchain. You do not need to provide any configuration steps for DevOps Insights.
* App name: The name of the app. The default app name is the same as your toolchain name.
* IBM Cloud API Key: The API key that is used to interact with the ibmcloud CLI tool in several tasks. Use one of the following methods to specify the API key that you want to use:



* Click the key icon to import an existing API key from a secrets vault of your choice.
* Copy and paste an existing API key.
* Click New to create an API key.
* Generate a new api-key if you don’t have an existing API key.



You can immediately save the generated API key to an existing secrets vault of your choice.
* Container registry region: The Container Registry region in which your container namespace is located.
* Container registry namespace: Select from the list of container namespaces in the associated Container Registry region.
* Code Engine region: The region in which your Code Engine project is located.
* Code Engine Resource Group: The Resource Group where your Code Engine project was created.
* Code Engine project: The name of the project that was created in Code Engine. Your app is deployed to this project.



Zoom

![Code Engine secure app deployment target details for Rolling or Blue-Green](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/code_engine_dep_target.png)

Figure 5. Code Engine secure app rolling deployment target details
2. Click Continue.







 Step 3: Add optional tool integrations 

You can add the IBM Cloud® DevOps Insights tool integration to your toolchain without any additional configuration.

[DevOps Insights](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-di_working) is included in the created toolchain. You do not need to provide any configuration steps for DevOps Insights. The continuous integration pipeline automatically uses the DevOps Insights instance that is included in the toolchain.
curl -X POST "https://iam.cloud.ibm.com/identity/token" -H "Content-Type: application/x-www-form-urlencoded" -d "grant_type=urn:ibm:params:oauth:grant-type:apikey&apikey=$IBMCLOUD_API_KEY" -u bx:bx
5. Run the Python script by using python3 <python-file-name> to destroy the resources that you created in the Schematics workspace in the IBM Cloud.
6. You get an activity ID in the response if the parameters passed as part of the request are valid. You should be able to see that the resources are deleted in the Schematics workspace that you created in the IBM Cloud console. If you don’t get a successful response, the error response contains the errors that you need to resolve. Resolve those errors and run the script until you are able to get a valid response and destroy the resources.
7. If you want to check the logs of the action, see [Retrieving action logs with Schematics API](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-retrieve-action-logs) to retrieve the logs. The response contains the status of the action, and it appears in either a COMPLETED or FAILED state.





 Example Python request 

 Destroy resources using Schematics Python API

import json, logging

from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
from ibm_schematics.schematics_v1 import SchematicsV1

logging.basicConfig()
logging.root.setLevel(logging.NOTSET)
logging.basicConfig(level=logging.NOTSET)

authenticator = IAMAuthenticator('<ibmcloud-api-key>')

schematics_service = SchematicsV1(authenticator = authenticator)

schematics_service.set_service_url('https://us.schematics.cloud.ibm.com')
* Run the following curl command to create a refresh token:



curl -X POST "https://iam.cloud.ibm.com/identity/token" -H "Content-Type: application/x-www-form-urlencoded" -d "grant_type=urn:ibm:params:oauth:grant-type:apikey&apikey=$IBMCLOUD_API_KEY" -u bx:bx
5. Run the Python script by using python3 <python-file-name> to destroy the resources that you created in the Schematics workspace in the IBM Cloud.
6. You get an activity ID in the response if the parameters passed as part of the request are valid. You should be able to see that the resources are deleted in the Schematics workspace that you created in the IBM Cloud console. If you don’t get a successful response, the error response contains the errors that you need to resolve. Resolve those errors and run the script until you are able to get a valid response and destroy the resources.
7. If you want to check the logs of the action, see [Retrieving action logs with Schematics API](https://cloud.ibm.com/docs/hpc-spectrum-scale?topic=hpc-spectrum-scale-retrieve-action-logs) to retrieve the logs. The response contains the status of the action, and it appears in either a COMPLETED or FAILED state.





 Example Python request 

 Destroy resources using Schematics Python API

import json, logging

from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
from ibm_schematics.schematics_v1 import SchematicsV1

logging.basicConfig()
logging.root.setLevel(logging.NOTSET)
logging.basicConfig(level=logging.NOTSET)

authenticator = IAMAuthenticator('<ibmcloud-api-key>')

schematics_service = SchematicsV1(authenticator = authenticator)
* Run the following curl command to create a refresh token:



curl -X POST "https://iam.cloud.ibm.com/identity/token" -H "Content-Type: application/x-www-form-urlencoded" -d "grant_type=urn:ibm:params:oauth:grant-type:apikey&apikey=$IBMCLOUD_API_KEY" -u bx:bx
5. Run the Python script by using python3 <python-file-name> to destroy the resources that you created in the Schematics workspace in the IBM Cloud.
6. You get an activity ID in the response if the parameters passed as part of the request are valid. You should be able to see that the resources are deleted in the Schematics workspace that you created in the IBM Cloud console. If you don’t get a successful response, the error response contains the errors that you need to resolve. Resolve those errors and run the script until you are able to get a valid response and destroy the resources.
7. If you want to check the logs of the action, see [Retrieving action logs with Schematics API](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-retrieve-action-logs) to retrieve the logs. The response contains the status of the action, and it appears in either a COMPLETED or FAILED state.





 Example Python request 

 Destroy resources using Schematics Python API

import json, logging

from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
from ibm_schematics.schematics_v1 import SchematicsV1

logging.basicConfig()
logging.root.setLevel(logging.NOTSET)
logging.basicConfig(level=logging.NOTSET)

authenticator = IAMAuthenticator('<ibmcloud-api-key>')

schematics_service = SchematicsV1(authenticator = authenticator)
You get an activity ID in the response if the parameters passed as part of the request are valid. You should be able to see that the resources are deleted in the Schematics workspace that you created in the IBM Cloud console. If you don’t get a successful response, the error response contains the errors that you need to resolve. Resolve those errors and run the script until you are able to get a valid response and destroy the resources.
7. If you want to check the logs of the action, see [Retrieving action logs with Schematics API](https://cloud.ibm.com/docs/hpc-openshift?topic=hpc-openshift-retrieve-action-logs&interface=api) to retrieve the logs. The response contains the status of the action, and it appears in either a COMPLETED or FAILED state.





 Example Python request 

 Destroy resources using Schematics Python API

import json, logging

from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
from ibm_schematics.schematics_v1 import SchematicsV1

logging.basicConfig()
logging.root.setLevel(logging.NOTSET)
logging.basicConfig(level=logging.NOTSET)

authenticator = IAMAuthenticator('<ibmcloud-api-key>')

schematics_service = SchematicsV1(authenticator = authenticator)

schematics_service.set_service_url('https://us.schematics.cloud.ibm.com')

logging.info("Started Deletion of Schematic Resources")

workspace_activity_destroy_result = schematics_service.destroy_workspace_command(
    w_id='<workspace-id>',
    refresh_token='<refresh-token>'
).get_result()

print(json.dumps(workspace_activity_destroy_result, indent=2))

logging.info("Completed Deletion of Schematic Resources")





 Example Python response
However, if you don’t know the geometries or you want to play safe to not exclude any geometries that might potentially fall outside the given bounding box (both are very common situations), you can use the whole earth as the bounding box by simply leaving the bbox parameter setting at None, which is the default value.
* Tile size: Defines the size of a tile in a tessellation index. The value is given by the length of the tile in the unit of meters. You should provide a tile size that is close to the size of your geometries for better performance. For example, if your geometries are 100 km2 (i.e. 10^8 m2), then 10^4 m could be a good value for tile size.

With a value for bounding box and tile size, you can now create the spatial index and import your geometries into the spatial index. Use the from_df function to move the geometries from a pandas DataFrame to a spatial index. For this, you only need to specify the name of the geometry ID column and the name of the geometry column. Set the third parameter, verbosity, which controls log processing, to error so that only summary and failure logs are displayed.

>>> tile_size = 100000
>>> si = stc.tessellation_index(tile_size=tile_size) we leave bbox as None to use full earth as boundingbox
>>> si.from_df(county_df, 'NAME', 'geometry', verbosity='error')
3221 entries processed, 3221 entries successfully added





3. Perform spatial index queries. For quering a spatial index, pyst provides the following different query APIs: contained_in, contained_in_with_info, containing, containing_with_info, intersects, intersects_with_info, within_distance, within_distance_with_info, nearest_neighbors, nearest_neighbors_with_info.

Sample queries:



* Which county does White Plains Hospital belongs to? Which county polygon contains the point location of White Plains Hospital?
* Note: If you want to delete the workspace but not the resources, then remove the destroy_resources parameter completely or set the destroy_resources parameter to False. If resources are already deleted, and if the destroy_resources parameter value is set to True, then the RESOURCE DELETE action will be in FAILED state.



5. Run the Python script by using python3 <python-file-name> to delete the workspace.
6. You get the status Started Deleting Schematic Workspace and Completed Deleting Schematic Workspace in response if the parameters passed as part of the request are valid. You should be able to see that the workspace is deleted in the Schematics that you created. If you don’t get a successful response, the error response contains the errors that you need to resolve. Resolve those errors and run the script until you are able to get a valid response and the workspace is deleted.







 Example Python request 

 Delete a workspace using Schematics Python API

import json, logging

from ibm_schematics.schematics_v1 import SchematicsV1
from ibm_cloud_sdk_core.authenticators import IAMAuthenticator

logging.basicConfig()
logging.root.setLevel(logging.NOTSET)
logging.basicConfig(level=logging.NOTSET)

authenticator = IAMAuthenticator('<ibmcloud-api-key>')

schematics_service = SchematicsV1(authenticator = authenticator)

schematics_service.set_service_url('https://us.schematics.cloud.ibm.com')

logging.info("Started Deleting Schematic Workspace")

workspace_delete_response = schematics_service.delete_workspace(
    w_id='<workspace id>',
    refresh_token='<refresh-token>',
    destroy_resources= True,
).get_result()

print(json.dumps(workspace_delete_response, indent=2))
* Note: If you want to delete the workspace but not the resources, then remove the destroy_resources parameter completely or set the destroy_resources parameter to False. If resources are already deleted, and if the destroy_resources parameter value is set to True, then the RESOURCE DELETE action will be in FAILED state.



5. Run the Python script by using python3 <python-file-name> to delete the workspace.
6. You get the status Started Deleting Schematic Workspace and Completed Deleting Schematic Workspace in response if the parameters passed as part of the request are valid. You should be able to see that the workspace is deleted in the Schematics that you created. If you don’t get a successful response, the error response contains the errors that you need to resolve. Resolve those errors and run the script until you are able to get a valid response and the workspace is deleted.







 Example Python request 

 Delete a workspace using Schematics Python API

import json, logging

from ibm_schematics.schematics_v1 import SchematicsV1
from ibm_cloud_sdk_core.authenticators import IAMAuthenticator

logging.basicConfig()
logging.root.setLevel(logging.NOTSET)
logging.basicConfig(level=logging.NOTSET)

authenticator = IAMAuthenticator('<ibmcloud-api-key>')

schematics_service = SchematicsV1(authenticator = authenticator)

schematics_service.set_service_url('https://us.schematics.cloud.ibm.com')

logging.info("Started Deleting Schematic Workspace")

workspace_delete_response = schematics_service.delete_workspace(
w_id="<workspace id>",
refresh_token="<refresh-token>",
destroy_resources= False,
).get_result()

print(json.dumps(workspace_delete_response, indent=2))
* Invoice Reference - Optionally, enter a reference description, such as a PO number or billing reference number.
* Rate Limit – Enter the speed of your connection in Mbps. Match the port speed created in the IBM Cloud console for the Direct Link service.
* Preferred A-End VLAN – Optionally, specify an unused VLAN ID for this connection. This must be a unique VLAN ID on this port and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport assigns one.



Alternatively, you can click Untag to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this port.

Zoom

![Connection Details page](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/dl//images/megaport_connection_details.png)

Connection Details page
7. Click Next. A Summary page appears that includes the monthly cost.

Zoom

![Summary page](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/dl//images/megaport_summary.png)

Summary page
8. Click Back to make changes, or click Add VXC.

After you have completed this configuration, you can configure additional VXCs, or proceed through the ordering process.
9. Review the details and click Order.

Zoom

!
[DevSecOps Cloud Object Storage Endpoint menu](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-cos-endpoint-menu.png)

Figure 13. DevSecOps Cloud Object Storage Endpoint menu

If you decide not to use Cloud Object Storage as an evidence locker, you can also set the required values after the creation of the toolchain by setting the cos-bucket-name, cos-endpoint environment variables in the CI Pipeline.





 Deploy 

The default behavior of the toolchain is to Clone existing pipeline that creates a new repository as IBM-hosted Git Repos and Issue Tracking Repository. If you want to link an existing Pipeline Repository for the toolchain, choose Use existing repository and provide it as input to Repository URL field. As noted earlier, the toolchain currently supports linking only to existing Git Repos and Issue Tracking repositories.



* App name:



The name of the application. - Default: hello-compliance-app





 IBM Cloud API Key 

The API key is used to interact with the ibmcloud CLI tool in several tasks. If you already created a cluster, an API to access the cluster and stored the key in a secure vault (any of Key Protect, Secrets Manager, or HashiCorp Vault), as prerequisite you can use the same in this step.



* Option-1: An existing key can be imported from an existing Secret Provider instance that is created as prerequisites (Key Protect Instance, Secret Manager Instance, or HashiCorp Vault) by clicking the key icon (Recommended)
* Option-2: An existing key can be copy and pasted (Not Recommended)
* Option-3: A new key can be created from here by clicking New +. Generate a new api-key if you don’t have one or copy an existing key to the field. The newly generated API key can be saved to an existing Key Protect instance.



The newly generated API key can be saved to an existing Key Protect instance.

Zoom

!
* [No ping from DNS servers](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-troubleshooting-bare-metalbm-ping-DNS-servers).





 Internet is blocked by firewall or gateway 

If you can't access the internet, your internet access might be blocked by your firewall or gateway (Vyatta, AT&T, Juniper, FortiGate).





 Public gateway IP isn't configured for the network card 

If the firewall is not an issue, check whether the public gateway IP is configured for the public network card and try pinging the public gateway. For more help, contact [support](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-gettinghelp).





 No ping from DNS servers 

If you configured DNS servers for the public network card, check whether you can ping IBM Cloud® DNS servers (10.0.80.11 and 10.0.80.12).

If you have Linux servers, add the following entries in the /etc/resolv.conf file:

nameserver 10.0.80.11 and nameserver 10.0.80.12







 Why does the portal show that my server is disconnected even though it's running? 

If your portal shows that the server is disconnected, but the server is running, it might be your firewall or gateway (Vyatta, AT&T, Juniper, FortiGate).

If your ping traffic is blocked, then the status of your servers shows "disconnected" in the portal. Check that your firewall rules allow ping traffic from IBM Cloud® IP ranges. For more information, see [IBM Cloud® IP ranges](https://cloud.ibm.com/docs/security-groups?topic=hardware-firewall-shared-ibm-cloud-ip-ranges).





 Why does ESXi server show Purple Screen of Diagnostics (PSOD) 

If you receive Purple Screen of Diagnostics (PSOD) on an ESXi server, it might be caused by one of the following reasons.



* A memory fault or error can cause a PSOD.



* Restart the server to clear the memory.
To ensure that your ListItems are not overridden and that each has a unique ID, recrawl your collection, or change the configuration settings for your data source so that your ListItems are assigned a unique ID.
* SharePoint Online cannot crawl Personal SiteCollections.



To successfully crawl Microsoft SharePoint Online, you must enable legacy authentication and Contribute level permissions. To enable legacy authentication, visit the [Azure portal](https://portal.azure.com/), or contact your SharePoint administrator. For assistance with enabling Contribute level permissions, you can also contact your SharePoint administrator.

If you created a SharePoint Online account after January 2020, two-factor authentication is enabled for your account, by default. To crawl your SharePoint Online collection, you must disable two-factor authentication. To view and change your multifactor authentication status, see [View the status for a user](https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-userstatesview-the-status-for-a-user) or [Change the status for a user](https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-userstateschange-the-status-for-a-user).





 Web Crawl 

You can use the web crawler to crawl public websites that don’t require a password. You can select how often you'd like Discovery to sync with the websites, the language, and the number of hops.



* Sync my data - You can choose to sync hourly, daily, weekly, or monthly.
* Select language - Choose the language of the websites from the list of supported languages. For the list of languages that Discovery supports, see [Language support](https://cloud.ibm.com/docs/discovery?topic=discovery-language-support). You should create a separate collection for each language.
* URL group to sync - Enter your URL and click the Add button to add it to the URL group. To specify the Crawl settings for this URL group, click the !
curl -X POST "https://iam.cloud.ibm.com/identity/token" -H "Content-Type: application/x-www-form-urlencoded" -d "grant_type=urn:ibm:params:oauth:grant-type:apikey&apikey=$IBMCLOUD_API_KEY" -u bx:bx
* Note: If you want to destroy the resources as well as delete the workspace, then set the destroy_resources parameter value to True. In this case, the resources are deleted first, and then the workspace is deleted.
* Note: If you want to delete the workspace but not the resources, then remove the destroy_resources parameter completely or set the destroy_resources parameter to False. If resources are already deleted, and if the destroy_resources parameter value is set to True, then the RESOURCE DELETE action will be in FAILED state.



5. Run the Python script by using python3 <python-file-name> to delete the workspace.
6. You get the status Started Deleting Schematic Workspace and Completed Deleting Schematic Workspace in response if the parameters passed as part of the request are valid. You should be able to see that the workspace is deleted in the Schematics that you created. If you don’t get a successful response, the error response contains the errors that you need to resolve. Resolve those errors and run the script until you are able to get a valid response and the workspace is deleted.







 Example Python request 

 Delete a workspace using Schematics Python API

import json, logging

from ibm_schematics.schematics_v1 import SchematicsV1
from ibm_cloud_sdk_core.authenticators import IAMAuthenticator

logging.basicConfig()
logging.root.setLevel(logging.NOTSET)
logging.basicConfig(level=logging.NOTSET)

authenticator = IAMAuthenticator('<ibmcloud-api-key>')

schematics_service = SchematicsV1(authenticator = authenticator)