vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For information about adding different types of Git repos to your toolchain, see [Configuring GitHub](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-github) and [Configuring GitLab](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-gitlab).



1. From the IBM Cloud console, click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg) and select DevOps. On the Toolchains page, click the toolchain to open its Overview page. Alternatively, on your app's Overview page, on the Continuous delivery card, click View toolchain. Then, click Overview.
2. Click Add tool.
3. In the Tool Integrations section, click Git Repos and Issue Tracking.
4. Select the server that you want to deploy code changes to. After you create the integration, you can edit it to manage the list of servers that you are authorized to work with. Click Manage Authorization to view a list of all of the servers and to delete the token that you provided to authorize with the server.
5. To create a copy of the Git repo, for the repository type, click Clone. Type a new repo name and the URL for the source repo.
6. Your username is automatically selected to assign ownership of this new integration to yourself. After the integration is created, another authorized user can reassign ownership of the integration to themself when they edit it.
7. If you want to create a private repo, select the Make this repository private checkbox.
8. If you want to use Issues for issue tracking, select the Enable Issues checkbox.
9.
Type the URL for the Mirror or Public registry that you use to combine multiple public and private npm registries. For example, this URL might be the URL of the virtual registry on your Nexus server that can access both your private registry and a cache of the npm global registry.
7. If you selected Maven repository, follow these steps:

a. Type the user ID that is associated with your repo.

b. Type the password that is associated with your repo.

c. Type the URL for your Nexus release repo, which is your private release repo on the Nexus server.

d. Type the URL for your Nexus snapshot repo, which is your private snapshot repo on the Nexus server.

e. Type the URL for the Mirror or Public repo that you use to combine multiple public and private Maven repos. For example, this URL might be the URL of the virtual repo on your Nexus server that can access both your private repos and a cache of the Maven central repo.
8. Click Create Integration.
9. From your toolchain's Overview page, on the Third-Party tools card, click the Nexus repo that you want to work with. The Nexus website opens, where you can view the contents of the repo.
10. Optional: If you are using a toolchain on IBM Cloud Public and you want to build your app by using Nexus with npm, configure your pipeline to add an npm build job. For instructions to configure the build job, see the [Configuring a Nexus npm build job in your pipeline](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-nexusconfig_nexus_npm) section.
11. Optional: If you are using a toolchain on IBM Cloud Public and you want to build your app by using Nexus with Maven, configure your pipeline to add a Maven build job.
Type the URL for the Mirror or Public registry that you use to combine multiple public and private npm registries. For example, this URL might be the URL of the virtual registry on your Nexus server that can access both your private registry and a cache of the npm global registry.
7. If you selected Maven repository, follow these steps:

a. Type the user ID that is associated with your repo.

b. Type the password that is associated with your repo.

c. Type the URL for your Nexus release repo, which is your private release repo on the Nexus server.

d. Type the URL for your Nexus snapshot repo, which is your private snapshot repo on the Nexus server.

e. Type the URL for the Mirror or Public repo that you use to combine multiple public and private Maven repos. For example, this URL might be the URL of the virtual repo on your Nexus server that can access both your private repos and a cache of the Maven central repo.
8. Click Create Integration.
9. From your toolchain's Overview page, on the Third-Party tools card, click the Nexus repo that you want to work with. The Nexus website opens, where you can view the contents of the repo.
10. Optional: If you are using a toolchain on IBM Cloud Public and you want to build your app by using Nexus with npm, configure your pipeline to add an npm build job. For instructions to configure the build job, see the [Configuring a Nexus npm build job in your pipeline](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-nexusconfig_nexus_npm) section.
11. Optional: If you are using a toolchain on IBM Cloud Public and you want to build your app by using Nexus with Maven, configure your pipeline to add a Maven build job.
As noted earlier, the toolchain currently supports linking only to existing Git Repos and Issue Tracking repositories.



* Repository URL: URL of the Inventory Repository configured in your CI Toolchain as captured in [Application Related Repositories](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-tekton-cd-compliancecd-app-repos).



Zoom

![DevSecOps inventory repository](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-cd-inventory-repo.png)

Figure 4. DevSecOps inventory repository





 Issues 

The default behavior of the toolchain is to Use existing issues repository to link an existing Issues Repository for the toolchain. As noted earlier, the toolchain currently supports linking only to existing Git Repos and Issue Tracking repositories.



* Repository URL: URL of the Issues Repository configured in your CI Toolchain as captured in [Application Related Repositories](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-tekton-cd-compliancecd-app-repos).



Zoom

![DevSecOps issues repository](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-cd-issues-repo.png)

Figure 5. DevSecOps issues repository





 Pipeline Configuration 

The repository contains custom scripts to run pipeline tasks in the CD Pipeline (.pipeline-config.yaml).
Testing is not complete for private repositories using Git tokens. Planned in November 2022 Delivered November 2022 
 Templates and modules in IBM private Gitlab using IAM token support Planned in December 2022 







 Beta release known issues 



Beta release known issues

 Issue Resolved Date 

 apply, destroy, and deletes return the generic message fullfilment_success on successful completion. 
 JSON output option not supported on commands. 







 Joining public slack channel 



 Steps to join public slack 

Following steps asks you to join the Schematics Blueprints beta public Slack channel.



* Click [IBM Cloud Schematics Slack](https://cloud.ibm.com/schematics/slack).
* Select Request to join Slack > Request Invite.
* A support case page is opened.
* Support Case Subject : Request invitation to public slack channel for Schematics Blueprints beta.
* Support Case Description: Invite my email address to the Schematics Blueprints beta public Slack channel
* Click Next.
* Click Submit case. Wait for 10 - 15 minutes to get access.
On the Overview page, scroll to the "Continuous delivery" card and click View toolchain. Your app's source will be saved in a repo that is hosted on IBM Cloud®. An open toolchain that uses that repo and a delivery pipeline to develop and deploy your app is also created. For more information about the Continuous Delivery service, see [Getting started with Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-getting-started).



Note: If a service that you bind to an app crashes, the app might stop running or have errors. IBM Cloud does not automatically restart the app to recover from these problems. Consider coding your app to identify and recover from outages, exceptions, and connection failures. See the Apps are not automatically restarted troubleshooting topic for more information.



 Options for working with apps 

After your app is created, you have a few options for continuing to add services to your app and to build and deploy your app.



 Using the ibmcloud cf command line interface 

Use the [ibmcloud cf command line interface](https://github.com/cloudfoundry/cligetting-started) to update your app, create a service instance, or bind the service to your app. You can also use the cloud-cli command line interface to create, update, and delete service offerings.





 Using the IBM Cloud user interface 

Use the IBM Cloud [user interface](https://cloud.ibm.com/resources) to build your app, including picking which services and runtimes to combine to solve your business problem.





 Using IBM Cloud® Continuous Delivery 

Use Continuous Delivery to automate builds, unit tests, deployments, and more. Edit and push code through the rich web based IDE. Create toolchains to enable tool integrations that support your development, deployment, and operation tasks. The Continuous Delivery service includes Delivery Pipeline, Eclipse Orion Web IDE, and Git Repos and Issue Tracking. For more information,see [Getting started with Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-getting-started).
![The Truck Tracker Solution](https://cloud.ibm.com/docs-content/v1/content/fcee192e52fce225776143bc6ccc3a023d1d193a/databases-for-etcd/includes/cloud-databases/includes/cloud-databases/images/TruckTrackerOS.png)

Figure 1. The Truck Tracker Solution

In a real-life scenario, your data generators (the truck's IoT devices) would have to find a way to communicate with the Event Streams application, probably using the MQTT protocol. We will simulate our trucks traveling around the country and sending data by using a script (producer.js) that will be generating a truck location every second by reading from a predefined set of lat/long pairs of a couple of "road trips" (LAToDallas.json and boulderToNYC.json) and feeding it into Event Streams.

This tutorial should take you about an hour to complete. It will not be cost-free because some of the IBM services we will use do not come with a free tier, but if you deprovision the services after completing it, you should not have to pay more than a few dollars.





 What you will need 

Before you begin, it's a good idea to install some necessary productivity tools:



* An [IBM Cloud](https://cloud.ibm.com/login) pay-as-you-go account (make sure it is [logged in to your account.](https://cloud.ibm.com/docs/cli?topic=cli-getting-startedstep4-configure-idt-env))
* The [IBM CLI](https://www.ibm.com/cloud/cli) - the command line interface to interact with the IBM API. You will need to make sure it has the following [plug-ins](https://cloud.ibm.com/docs/cli?topic=cli-plug-ins):



* openshift (oc)
* container registry (cr)
With Diego, the proxy is not necessary because Diego provides the capability to ssh directly to your app and set up port forwarding.

The noproxy utility only applies to apps that run in a Diego cell.





 hc 

The (hc) Health Center agent enables your app to be monitored by the Health Center client.

When you have the Health Center agent enabled, you can analyze the performance of your Liberty apps by using the IBM Monitoring and Diagnostic Tools. For more information see [How to analyze the performance of Liberty Java in IBM Cloud](https://www.ibm.com/blogs/cloud-archive/2015/07/how-to-analyze-performance-in-bluemix/).

The hc utility starts proxy.





 Using hc with noproxy 

The hc utility can be used in conjunction with noproxy. To use Health Center with noproxy, first establish port forwarding by using the ibmcloud cf ssh command. For example:

ibmcloud cf ssh -N -T -L 1883:127.0.0.1:1883 <appName>

To connect with the Health Center client, use a [MQTT connection](http://www.ibm.com/support/knowledgecenter/SS3KLZ/com.ibm.java.diagnostics.healthcenter.doc/topics/connectingtojvm.html) and specify the host as 127.0.0.1 and port as 1883.
* [Using Buildah to authenticate with the registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_apikey_auth_example_other_buildah)
* [Using Docker to authenticate with the registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_apikey_auth_docker)
* [Using Podman to authenticate with the registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_apikey_auth_example_other_podman)
* [Using Skopeo to authenticate with the registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_apikey_auth_other_example_skopeo)





* [Accessing your namespaces interactively](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_interactive)



* [Using Buildah to access your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_interactive_auth_buildah)
* [Using Docker to access your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_interactive_auth_docker)
* [Using Podman to access your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_interactive_auth_podman)
* [Using Skopeo to access your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_interactive_auth_skopeo)
[The Truck Tracker Solution](https://cloud.ibm.com/docs-content/v1/content/5561b38c6df9e8168523d143eaf64ab6acd7b600/cloud-databases/images/TruckTrackerOS.png)

Figure 1. The Truck Tracker Solution

In a real-life scenario, your data generators (the truck's IoT devices) would have to find a way to communicate with the Event Streams application, probably using the MQTT protocol. We will simulate our trucks traveling around the country and sending data by using a script (producer.js) that will be generating a truck location every second by reading from a predefined set of lat/long pairs of a couple of "road trips" (LAToDallas.json and boulderToNYC.json) and feeding it into Event Streams.

This tutorial should take you about an hour to complete. It will not be cost-free because some of the IBM services we will use do not come with a free tier, but if you deprovision the services after completing it, you should not have to pay more than a few dollars.





 What you will need 

Before you begin, it's a good idea to install some necessary productivity tools:



* An [IBM Cloud](https://cloud.ibm.com/login) pay-as-you-go account (make sure it is [logged in to your account.](https://cloud.ibm.com/docs/cli?topic=cli-getting-startedstep4-configure-idt-env))
* The [IBM CLI](https://www.ibm.com/cloud/cli) - the command line interface to interact with the IBM API. You will need to make sure it has the following [plug-ins](https://cloud.ibm.com/docs/cli?topic=cli-plug-ins):



* openshift (oc)
* container registry (cr)



* Make sure you have access to a Mac or Linux terminal.
* [Clean up for Kafka subscription tutorial](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialtutkafka-delete-subscription)
* [Next steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialnextsteps-kafkatut)



[Sending GitHub events to an application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-github-event-webhooksgithub-event-webhooks)



* [Prerequisites](https://cloud.ibm.com/docs/codeengine?topic=codeengine-github-event-webhooksgew-prerequisites)
* [Create an application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-github-event-webhooksgew-create-app)
* [Create a webhook](https://cloud.ibm.com/docs/codeengine?topic=codeengine-github-event-webhooksgew-create-webhook)
* [Test your GitHub event](https://cloud.ibm.com/docs/codeengine?topic=codeengine-github-event-webhooksgew-test-webhook)
* [Clean up](https://cloud.ibm.com/docs/codeengine?topic=codeengine-github-event-webhooksgithub-clean-up)







 Deploying Cloud Foundry applications in Code Engine: Getting started 

[Deploying Cloud Foundry applications in Code Engine: Getting started](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-tutorialmigrate-cf-ce-tutorial)
createToolOptions := toolchainClient.NewCreateToolOptions("01234567-89ab-cdef-0123-456789abcdef", "slack")
createToolOptions.SetParameters(slackParameters)
slackTool, response, err := toolchainClient.CreateTool(createToolOptions)

The following table lists and describes each of the secret reference values that are used in the previous example.



Table 1. Secret reference values

 Value Description 

 my-kms-tool-integration The name of the Key Protect tool integration in the toolchain. It is not the name of the Key Protect service instance. 
 my-slack-webhook The name of the standard key that is managed in the Key Protect service instance. 







 Using secrets references by CRN 

The following example demonstrates how to use a secrets reference by CRN secret. It shows how to create a Slack tool integration with an API token (Slack webhook) that is stored in an instance of Secrets Manager. This example assumes that the toolchain already contains a Secrets Manager tool integration and that an IAM service-to-service authorization policy from the source toolchain to the target Secrets Manager service instance is in place.



* Curl
* Java
* Node
* Python
* Go



curl -X POST https://api.us-south.devops.cloud.ibm.com/toolchain/v2/toolchains/01234567-89ab-cdef-0123-456789abcdef/tools -H "Authorization: Bearer $TOKEN" -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{
"tool_type_id": "slack",
"parameters": {
\n The URL to the license is [https://creativecommons.org/licenses/by/3.0/legalcode](https://creativecommons.org/licenses/by/3.0/legalcode).



* GO GOPHER[google/golang](https://storage.googleapis.com/golang/go1.14.2.linux-amd64.tar.gz)
* THE LOGO AND MASCOT[google/golang](https://storage.googleapis.com/golang/go1.14.2.linux-amd64.tar.gz)
* H2DEMO[golang/x/net](https://github.com/golang/net/commit/d3edc9973b7eb1fb302b0ff2c62357091cea9a30)
* DIR.TMPL[golang/x/tools](https://github.com/golang/tools/commit/de023d59a5d12fe28f29c985eb1f744aae7e7d73)
* H2.DEMO/TMPL.GO[protoc-gen-validate](https://github.com/bufbuild/protoc-gen-validate/releases/tag/v0.1.0)







 Creative Commons Attribution 4.0 

The Program includes some or all the following works licensed under the Creative Commons. \n The URL to the license is [https://creativecommons.org/licenses/by/4.0/legalcode](https://creativecommons.org/licenses/by/4.0/legalcode).

SWAGGER PETSTORE[go-openapi/validate](https://github.com/go-openapi/validate/releases/tag/v0.19.8)





 Creative Commons Attribution Share Alike 1.0 Generic 

The Program includes some or all the following works licensed under the Creative Commons.
![The Truck Tracker Solution](https://cloud.ibm.com/docs-content/v1/content/3505da55c475bf1edbe3eb3496324ba13941b783/databases-for-postgresql/includes/cloud-databases/includes/cloud-databases/images/TruckTrackerOS.png)

Figure 1. The Truck Tracker Solution

In a real-life scenario, your data generators (the truck's IoT devices) would have to find a way to communicate with the Event Streams application, probably using the MQTT protocol. We will simulate our trucks traveling around the country and sending data by using a script (producer.js) that will be generating a truck location every second by reading from a predefined set of lat/long pairs of a couple of "road trips" (LAToDallas.json and boulderToNYC.json) and feeding it into Event Streams.

This tutorial should take you about an hour to complete. It will not be cost-free because some of the IBM services we will use do not come with a free tier, but if you deprovision the services after completing it, you should not have to pay more than a few dollars.





 What you will need 

Before you begin, it's a good idea to install some necessary productivity tools:



* An [IBM Cloud](https://cloud.ibm.com/login) pay-as-you-go account (make sure it is [logged in to your account.](https://cloud.ibm.com/docs/cli?topic=cli-getting-startedstep4-configure-idt-env))
* The [IBM CLI](https://www.ibm.com/cloud/cli) - the command line interface to interact with the IBM API. You will need to make sure it has the following [plug-ins](https://cloud.ibm.com/docs/cli?topic=cli-plug-ins):



* openshift (oc)
* container registry (cr)
[The Truck Tracker Solution](https://cloud.ibm.com/docs-content/v1/content/99dae60bd0de1987ffcce4822e29b2bcdefe3a43/databases-for-mysql/includes/cloud-databases/includes/cloud-databases/images/TruckTrackerOS.png)

Figure 1. The Truck Tracker Solution

In a real-life scenario, your data generators (the truck's IoT devices) would have to find a way to communicate with the Event Streams application, probably using the MQTT protocol. We will simulate our trucks traveling around the country and sending data by using a script (producer.js) that will be generating a truck location every second by reading from a predefined set of lat/long pairs of a couple of "road trips" (LAToDallas.json and boulderToNYC.json) and feeding it into Event Streams.

This tutorial should take you about an hour to complete. It will not be cost-free because some of the IBM services we will use do not come with a free tier, but if you deprovision the services after completing it, you should not have to pay more than a few dollars.





 What you will need 

Before you begin, it's a good idea to install some necessary productivity tools:



* An [IBM Cloud](https://cloud.ibm.com/login) pay-as-you-go account (make sure it is [logged in to your account.](https://cloud.ibm.com/docs/cli?topic=cli-getting-startedstep4-configure-idt-env))
* The [IBM CLI](https://www.ibm.com/cloud/cli) - the command line interface to interact with the IBM API. You will need to make sure it has the following [plug-ins](https://cloud.ibm.com/docs/cli?topic=cli-plug-ins):



* openshift (oc)
* container registry (cr)



* Make sure you have access to a Mac or Linux terminal.
It is recommended to configure your SSH public key to simplify the command line interactions with the Git repositories.



1. [Use these instructions](https://us-south.git.cloud.ibm.com/help/user/ssh.mdgenerate-an-ssh-key-pair) to generate a new SSH key pair if you don't have one.
2. [Add your SSH public key](https://us-south.git.cloud.ibm.com/help/user/ssh.mdadd-an-ssh-key-to-your-gitlab-account) to your Git settings in the region where you plan to host your Git repositories, such as [Dallas (us-south.git.cloud.ibm.com)](https://us-south.git.cloud.ibm.com/-/profile/keys), [London (eu-gb.git.cloud.ibm.com)](https://eu-gb.git.cloud.ibm.com/-/profile/keys) or [Frankfurt (eu-de.git.cloud.ibm.com)](https://eu-de.git.cloud.ibm.com/-/profile/keys).



To verify the configuration:



1. Create a new private project in GitLab, select the option to initialize the repository with a README.
2. Checkout the project from the command line by cloning with the SSH link.
3. Update the README file.
4. Commit and push the changes.









 Cloud Shell 



 oc 

Follow these steps if you need to use another version of the OpenShift CLI than the one pre-installed:



1. Download the latest stable 4.x OpenShift CLI (oc)

curl https://mirror.openshift.com/pub/openshift-v4/clients/ocp/stable/openshift-client-linux.tar.gz --output oc.tar.gz
2. Extract oc.tar.gz: