vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [For JavaScript](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composerinstall_composer_js)
* [For Python](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composerinstall_composer_python)



* [Configuring and running compositions in Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composerrun)
* [Extending sequences with Composer](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composerextending)



* [Sequences without Composer](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composersequences-without-composer)
* [Sequences with Composer](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composersequences-with-composer)
* [Error handling for a sequence](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composererror-handling)
* [Conditional branching for a sequence](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composerconditional-branch)
* [Loops in Composer](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composerloop)
* [Inline definition of Actions within a composition](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composerinline-def)



* [Using other combinator definitions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composercombinator-def)
Develop and deploy an app by using IBM Cloud Satellite 

In this tutorial, you learn how to create an open toolchain by using IBM Cloud® Continuous Delivery and deploy your app on [Satellite](https://cloud.ibm.com/docs/satellite?topic=getting-started). You also learn how toolchains are implemented in the Continuous Delivery service and how to develop and deploy a simple web application (app) by using toolchains.

IBM Cloud Satellite brings public cloud services to any environment, allowing customers with stringent regulatory requirements to use the flexibility and agility of these services for their secure on-premises data center. Continuous Delivery uses [Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-cluster-config) to deploy an app across a group of clusters in IBM Cloud Satellite. With Satellite Config, you create a configuration to specify which Kubernetes resources you want to deploy to a cluster group of Kubernetes or Red Hat® OpenShift® on IBM Cloud® clusters that are running in your Satellite location or in IBM Cloud.

The toolchain that is used in this tutorial implements standard DevOps practices such as code scanning, acceptance tests, Git repos, and continuous integration and continuous delivery capabilities. After you create clusters and associate them with a Continuous Delivery cluster group, create a toolchain to change your app's code and push the change to the Git Repos and Issue Tracking repo. When you push changes to your repo, the Tekton-based delivery pipeline automatically builds and deploys the code.

[Tekton](https://www.ibm.com/cloud/blog/tekton-a-modern-approach-to-continuous-delivery) is an open source, vendor-neutral, Kubernetes-native framework that you can use to build, test, and deploy apps. Tekton provides a set of shared components for building [continuous integration](https://www.ibm.com/garage/method/practices/code/practice_continuous_integration/) and [continuous delivery](https://www.ibm.com/garage/method/practices/deliver/practice_continuous_delivery/) systems.
To add commands and arguments by using the CLI, add the --cmd and --args options to your [job create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-create) or your [jobrun submit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-submit) command.

For more information about defining commands and arguments, see [Defining commands and arguments for your Code Engine workloads](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cmd-args).





 Creating and running a job with environment variables 

You can define and set environment variables as key-value pairs that can be used by your job at run time.

You can define environment variables when you create your job, or when you update an existing job from the console or with the CLI. You can create environment variables for your jobs that fully reference a configmap (or secret) or reference individual keys in a configmap (or secret).

For more information about defining environment variables, see [Working with environment variables](https://cloud.ibm.com/docs/codeengine?topic=codeengine-envvar).





 Creating and running a job with secrets and configmaps 

In Code Engine, secrets and configmaps can be used by your job by using environment variables.

Both secrets and configmaps are key-value pairs. When mapped to environment variables, the NAME=VALUE relationships are set such that the name of the environment variable corresponds to the "key" of each entry in those maps, and the value of the environment variable is the "value" of that key.

Your job can use environment variables to fully reference a configmap (or secret) or reference individual keys in a configmap (or secret).
* UI
* API
* Terraform







 Creating toolchains with Git 

You can use a template that contains either a Git Repos and Issue Tracking or GitHub tool integration as a starting point to create a toolchain that you can add Git repositories (repos) to. Alternatively, you can start with either an empty toolchain or an existing toolchain and then add a Git Repos and Issue Tracking or GitHub tool integration to it.

To see which toolchain templates contain the Git Repos and Issue Tracking or GitHub tool integrations, see [Toolchain availability, templates, and tutorials](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd_abouttemplates).



 Creating a toolchain from a template with Git Repos and Issue Tracking or GitHub by using the console 

You can use a template as a starting point to [create a toolchain](https://cloud.ibm.com/devops/create) that includes either a Git Repos and Issue Tracking or GitHub tool integration. Learn more about how to use the templates from the [IBM Cloud Garage Method](https://www.ibm.com/cloud/architecture/toolchains).



1. Log in to [IBM Cloud](http://cloud.ibm.com).
2. 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.
3. On the DevOps dashboard, on the Toolchains page, click Create a Toolchain.
4. On the Create a Toolchain page, click a toolchain template.
5. Review the diagram of the toolchain that you are about to create. The diagram shows each tool integration in its lifecycle phase in the toolchain.
For more information about Object Storage instances, see [Getting started with IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage).
4. Configure your Object Storage CRN that you found with the previous step to specify an Object Storage instance to work with. Be sure to copy the entire ID, starting with crn:. This examples uses the --force option to force the configuration to use the specified CRN, which might be helpful if you have more than one Object Storage instance.

ibmcloud cos config crn --crn CRN --force

Example output

Saving new Service Instance ID...
OK
Successfully stored your service instance ID.
5. Identify a bucket to subscribe to. To see a list of buckets that are associated with your Object Storage instance,

ibmcloud cos buckets

To create a bucket,

ibmcloud cos bucket-create -bucket BUCKET_NAME
6. Identify the location and plan of the Object Storage bucket; for example use the mybucket bucket.

ibmcloud cos bucket-location-get --bucket mybucket

Example output

Details about bucket mybucket:
Region: us-south
Class: Standard



Your Object Storage bucket must be a regional bucket that is located in the same region as your Code Engine project.





 Step 2: Assigning the Notifications Manager role to Code Engine 

Before you can create an Object Storage subscription, you must assign the Notifications Manager role to a Code Engine project. As a Notifications Manager, Code Engine can view, modify, and delete notifications for an Object Storage bucket.

Only account administrators can assign the Notifications Manager role.



1. Identify the Code Engine project that you want to use. You can use the [ibmcloud ce project list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-list) command to display a list of projects.
(https://cloud.ibm.com/docs/devsecops?topic=devsecops-tutorial-cd-toolchain)[Part 4: Set up a Continuous Compliance (CC) toolchain Part 4 of a 4-part tutorial series: Use the CC toolchain template to ensure that your deployed artifacts and their source repositories are always compliant.](https://cloud.ibm.com/docs/devsecops?topic=devsecops-tutorial-cc-toolchain)[Introduction to DevSecOps Learn about DevSecOps, which includes the automation of security and compliance controls as part of continuous integration and continuous deployment processes.](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops_intro)[Working with incident issues Learn how to create, store, and update incident issues as part of the Continuous Integration and Continuous Compliance pipelines.](https://cloud.ibm.com/docs/devsecops?topic=devsecops-incident-issues)

 Video library 

[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/devsecops//images/CI_toolchain_thumbnail.png)<br><br>Getting Started with DevSecOps in IBM Cloud - Part 1 - Continuous Integration Toolchain](https://video.ibm.com/embed/recorded/130714354)[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/devsecops//images/CD_toolchain_thumbnail.png)<br><br>Getting Started with DevSecOps in IBM Cloud - Part 2 - Continuous Deployment Toolchain](https://video.ibm.com/embed/recorded/130714358)

 Learn more 

[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>!
ibmcloud ce configmap create --name myliteralconfigmap2 --from-literal TARGET=Stranger
2. [Deploy an app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-appdeploy-app-cli) and reference the myliteralconfigmap configmap. For this example, create an app that uses the hello image. When a request is sent to this sample app, the app reads the environment variable TARGET and prints Hello ${TARGET}. If this environment variable is empty, Hello World is returned. Reference the myliteralconfigmap configmap. For more information about the code that is used for this example, see [hello](https://github.com/IBM/CodeEngine/tree/main/hello).

ibmcloud ce app create --name myhelloapp --image icr.io/codeengine/hello --env-from-configmap myliteralconfigmap
3. Call the application. The app returns Hello Sunshine, which is the value for the TARGET key that is specified in the myliteralconfigmap configmap.

curl https://myhelloapp.d484a5d6-d10d.us-south.codeengine.appdomain.cloud

Example output

Hello Sunshine
4. Update the app again to use the myliteralconfigmap2 configmap.

When you update an application or job with an environment variable that fully references a configmap (or secret) to fully reference a different configmap (or secret), full references override other full references in the order in which they are set (the last referenced set overrides the first set).

ibmcloud ce app update --name myhelloapp --env-from-configmap myliteralconfigmap2

Example output

Updating application 'myhelloapp' to latest revision.
[...]
For example, "{"object-store-rg-e": "CLOUD_OBJECT_STORAGE"}. This value must be in base64. 







 Troubleshooting toolchain issues 

Troubleshoot your Code Engine toolchain with the following topics.



* [Debugging your Code Engine toolchain](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-toolchain-ce).
* [Troubleshooting for toolchains](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-troubleshoot-toolchains).
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

CREATIVE COMMONS ATTRIBUTION SHARE ALIKE 2.0 GENERIC

The Program includes some or all of the following works licensed under
the Creative Commons.
The url to the license is https://creativecommons.org/licenses/by-sa/2.0/legalcode

THREEBYTEUTF8 THAI [golang.org/x/text]
(https://proxy.golang.org/golang.org/x/text/@v/v0.3.6-0.20210227105805-e3aa4adf54f6.zip)

END OF CREATIVE COMMONS ATTRIBUTION SHARE ALIKE 2.0 GENERIC NON-IBM-LICENSE INFORMATION
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

CREATIVE COMMONS ATTRIBUTION SHARE ALIKE 2.5 GENERIC

The Program includes some or all of the following works licensed under
the Creative Commons.
The url to the license is https://creativecommons.org/licenses/by-sa/2.5/legalcode

CASES/MAP_TEST.GO [golang.org/x/text]
(https://proxy.golang.org/golang.org/x/text/@v/v0.3.6-0.20210227105805-e3aa4adf54f6.zip)

END OF CREATIVE COMMONS ATTRIBUTION SHARE ALIKE 2.5 GENERIC NON-IBM-LICENSE INFORMATION
import com.ibm.cloud.continuous_delivery.cd_toolchain.v2.model.;
...
CdToolchain toolchainService = CdToolchain.newInstance();
CreateToolOptions createToolOptions = new CreateToolOptions.Builder()
.name({tool_name})
.parameters({tool_parameters})
.toolchainId({toolchain_id})
.toolTypeId({tool_type_id})
.build();
Response<ToolchainToolPost> response = toolchainService.createTool(createToolOptions).execute();
ToolchainToolPost tool = response.getResult();

const CdToolchainV2 = require('@ibm-cloud/continuous-delivery/cd-toolchain/v2');
const toolchainService = CdToolchainV2.newInstance();
...
(async() => {
const toolPrototypeModel = {
toolchainId: {toolchain_id},
toolTypeId: {tool_type_id},
name: {tool_name},
parameters: {tool_parameters}
};
const response = await toolchainService.createTool(toolPrototypeModel);
})();

from ibm_continuous_delivery.cd_toolchain_v2 import CdToolchainV2
...
toolchain_service = CdToolchainV2.new_instance()
tool = toolchain_service.create_tool(
name = {tool_name},
toolchain_id = {toolchain_id},
tool_type_id = {tool_type_id},
parameters = {tool_parameters}
)

import (
In this step, you create a Develop a Code Engine App toolchain. The target Code Engine project is configured during the toolchain setup by using your IBM Cloud API key and your Code Engine project name. You can change these settings later by updating the Delivery Pipeline configuration. Any code that is merged into the target Git repo branch is automatically built, validated, and deployed into the Code Engine project.

To create a Develop a Code Engine App toolchain, click

[![Create toolchain](https://cloud.ibm.com/docs-content/v1/content/efbf7b33e3aca029f69f9244bced9dd4d8acb848/apps/includes/ContinuousDelivery/includes/ContinuousDelivery/images/create_toolchain_button.png)](https://cloud.ibm.com/devops/setup/deploy?repository=https://github.ibm.com/open-toolchain/code-engine-toolchain&env_id=ibm:yp:us-south)

Alternatively, from the IBM Cloud console, click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/efbf7b33e3aca029f69f9244bced9dd4d8acb848/apps/includes/ContinuousDelivery/includes/ContinuousDelivery/images/icon_hamburger.svg), and select DevOps. On the Toolchains page, click Create a Toolchain. On the Create a Toolchain page, click Develop a Code Engine App.



 Configure the toolchain name and region 



1. On the Welcome screen, review the default information for the toolchain settings. The toolchain's name identifies it in IBM Cloud. Make sure that the toolchain's name is unique within your toolchains for the same region and resource group in IBM Cloud.

The toolchain region can differ from the cluster and registry region.

Zoom

!
For more information about the code that is used for this example, see [helloworld](https://github.com/IBM/CodeEngine/tree/main/helloworld).
7. Select Source code.
8. Click Specify build details.
9. Accept the default for each page, clicking Next and then Done.
10. Click Create.



After your build run is submitted, the built container image is sent to Container Registry and then your application pulls the image and deploys for you. After the application status changes to Ready, you can try it out. Click Test application and then click Send request in the Test application pane. To open the application in a web page, click Application URL.

Example output

Hello World from:
___ __ ____ ____
/ __)/ ( ( __)
( (__( O )) D ( ) _)
___)__/(____/(____)
____ __ _ ___ __ __ _ ____
( __)( ( / __)( )( ( ( __)
) _) / /( (_ )( / / ) _)
(____)_)__) ___/(__)_)__)(____)
Some Env Vars:
--------------
CE_APP=myapp
CE_DOMAIN=us-south.codeengine.appdomain.cloud
CE_SUBDOMAIN=abcdabcdab
HOME=/root
HOSTNAME=myapp-00001-deployment-6db6d89dc7-k6qc7
K_REVISION=myapp-00001
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PORT=8080
PWD=/
SHLVL=1
(Author Vic Shóstak) (https://proxy.golang.org/github.com/gofiber/fiber/v2/@v/v2.10.0.zip)<-- </section "id="section-CC-BY-SA-4.0" "> --><-- <section "id="section-GPL-V3" "> --> GNU GENERAL PUBLIC LICENSE, VERSION 3 The Program includes some or all of the following licensed to you as Separately Licensed Code under the GNU General Public License. For copies of the source code for this software, send an email to deepika.kothamasu@in.ibm.com]deepika_.kothamasu_in_.ibm_.com] identifying the IBM product and the GPL-licensed program for which you are requesting the source code.ACLOCAL Thrift], AX_LUA (GPL V3 WITH AUTOCONF EXCEPTION) Thrift] ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/>Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.PreambleThe GNU General Public License is a free, copyleft license for software and other kinds of works.The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors.
You can use the IBM Cloud CLI to analyze your code for vulnerabilities and compliance with certain rules. Code Risk Analyzer is available in all IBM Cloud regions where toolchains are supported. For more information about Code Risk Analyzer, see [Code Risk Analyzer plug-in](https://cloud.ibm.com/docs/code-risk-analyzer-cli-plugin).

This image is built on Ubuntu version 20.04. If you need to use a different version of node.js, use nvm install v<node version> at the beginning of your script. This image now contains the Terraform CLI.

Support for helm2 was discontinued on 13 November 2020. The helm tool within this image is the latest in the 3.x branch. The helm3 tool is now named helm.

This image includes the following tools:

 node
v18.16.0

 npm
9.5.1

 jq
jq-1.6

 yq
yq version 2.4.1

 yq3
yq version 3.4.1

 yq4
yq (https://github.com/mikefarah/yq/) version v4.34.1

 kubectl
v1.25.8

 buildctl
buildctl github.com/moby/buildkit v0.11.6 2951a28cd7085eb18979b1f710678623d94ed578

 helm
v3.12.0+gc9f554d

 ibmcloud
ibmcloud version 2.16.0+492aff3-2023-04-06T16:13:44+00:00

 ibmcloud plugins
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.67 false
cloud-internet-services[cis] 1.14.11 true
code-engine[ce] 1.43.5 true
Add the new example by using the same syntax you use to define examples when creating a new training-data query. The following command example does not include a cross reference.

curl -u -X POST -u "4ba1624f-48b6-484a-8e32-18d1c205c1fa":"qUy3B0CbGf9G" -H "Content-Type: application/json" -d
'{
"document_id": "46b52fdc-3a72-4700-9849-ac217532b373",
"relevance": 3
}' "{url}/v1/environments//a56dd9b4-040b-4ea3-a736-c1e7a467e191/collections/99040100-fe6a-4782-a4f5-28f9eee30850/training_data/484baad4-d440-44b7-a0dd-70bb2ac77baa?version=2019-04-30"
3. Verify that the new example is added to the training-data query by again [listing the collection's training-data queries](https://cloud.ibm.com/apidocs/discoverylist-training-data):

curl -u "4ba1624f-48b6-484a-8e32-18d1c205c1fa":"qUy3B0CbGf9G" "{url}/v1/environments/a56dd9b4-040b-4ea3-a736-c1e7a467e191/collections/99040100-fe6a-4782-a4f5-28f9eee30850/training_data?version=2019-04-30"

The JSON that is returned is in the following format:

{
"query_id": "484baad4-d440-44b7-a0dd-70bb2ac77baa",
* Set up your [Code Engine CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli) environment.
* [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* Your source must be in an accessible location on your local workstation.



This example uses the https://github.com/IBM/CodeEngine samples; in particular, the helloworld sample.



1. Download the https://github.com/IBM/CodeEngine sample source to your local workstation with the following command.

git clone https://github.com/IBM/CodeEngine
2. Change to the CodeEnginehelloworld directory.
3. From the CodeEnginehelloworld directory, create the myjob-local job, which uses an image that is built from the CodeEnginehelloworld source on your local workstation. This command automatically builds and pushes the image to an IBM Cloud Container Registry namespace in your account. If you do not have an existing Container Registry namespace, Code Engine automatically creates one for you. By adding the --wait option, this specifies for the job create to wait for the image build to complete.

ibmcloud ce job create --name myjob-local --build-source . --wait

The . indicates the build source is located in your current working directory.

Example output

Creating job 'myjob-local'...
Packaging files to upload from source path '.'...
Submitting build run 'myjob-local-run-220420-150457582'...
Creating image 'private.us.icr.io/ce--abcde-glxo4kabcde/job-myjob-local'...
Waiting for build run to complete...
Build run status: 'Running'
Build run completed successfully.
* [Get the Code ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://github.com/IBM/pixiedust-facebook-analysis?cm_sp=IBMCode-_-discover-hidden-facebook-usage-insights-_-Get-the-Code)
* [View the Demo ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.youtube.com/watch?v=UIkjFo9o3vI&cm_sp=IBMCode-_-discover-hidden-facebook-usage-insights-_-View-the-Demo)







 Extend Watson text classification 

Use the Python NLTK toolkit and IBM DSX to achieve the desired text classification results.



* [Learn more ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://developer.ibm.com/patterns/extend-watson-text-classification/)
* [Get the Code ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://github.com/IBM/watson-document-classifier?cm_sp=Developer-_-extend-watson-text-classification-_-Get-the-code)
* [View the Demo ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://youtu.be/kp8dcM9AKrA?cm_sp=Developer-_-extend-watson-text-classification-_-Watch-the-video)







 Fingerprinting personal data from unstructured text 

Build a custom model using Watson Natural Language Understanding and Watson Knowledge Studio.



* [Learn more !