vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can specify the Coverage runner (such as JaCoCo, and Cobertura), the location of the Coverage result file, and the Coverage result directory, relative to the Working directory. 
 Gradle Builds by using Gradle. Pipeline image version: Runs in a container by using a built-in docker image, which provides various built-in commands. To adopt newer versions of those commands, use a newer image version.<br><br>Build script: Runs in a new Ubuntu shell whenever the job runs. In the script field, enter a script or reference scripts that are stored in to your project’s source control.<br><br>Working directory: Specifies the directory where the script is run.<br><br>Build archive directory - Specifies the directory that contains the job's output to be archived for use by a subsequent stage.<br><br>Enable test report: Select this checkbox to specify that the build job runs tests that produce result files in JUnit XML format. A report based on the result files is displayed on the Tests tab of the Job Results page. If any tests fail, the job is marked as failed.<br><br>Enable code coverage report: Select this checkbox to show more fields that you can use for the code coverage report. You can specify the Coverage runner (such as JaCoCo, and Cobertura), the location of the Coverage result file, and the Coverage result directory, relative to the Working directory. 
 Grunt Builds by using Grunt. Pipeline image version: Runs in a container by using a built-in docker image that provides various built-in commands. To adopt newer versions of those commands, use a newer image version.<br><br>Build script: Runs in a new Ubuntu shell whenever the job runs. In the script field, enter a script or reference scripts that are stored in to your project’s source control.<br><br>Working directory: Specifies the directory where the script is run.<br><br>Build archive directory: Specifies the directory that contains the job's output to archive for use by a subsequent stage.<br><br>Enable test report: Select this checkbox to specify that the build job runs tests that produce result files in JUnit XML format.
If you specify the --wait option, the application update waits for a maximum time in seconds, as set by the --wait-timeout option, for the application to become ready. If the application is not ready within the specified --wait-timeout period, the application create fails. This value is optional. The default value is true.

--wait-timeout, --wto
: The length of time in seconds to wait for the application to be updated. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 600.





 Example 

ibmcloud ce application update --name myapp --image icr.io/codeengine/hello





 Example output 

Updating application 'myapp' to latest revision.
[...]
Run 'ibmcloud ce application get -n myapp' to check the application status.
OK

https://myapp.4svg40kna19.us-south.codeengine.appdomain.cloud









 Build commands 

A build, or image build, is a mechanism that you can use to create a container image from your source code. Code Engine supports building from a Dockerfile and Cloud Native Buildpacks. Use build commands to create, display details, update, and delete build configurations. After you create a build configuration, one or more [buildrun commands](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-buildrun) can be submitted based on the build configuration.

You must be within the context of a [project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project) before you use build commands.

For more information about working with builds, see [Building a container image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-image).

You can use either build or bd in your build commands.
Defining commands and arguments for your workloads 

When you create a container image for your IBM Cloud® Code Engine workloads, you can define commands and arguments for your job or application to use at run time.

Container images include two pieces of metadata that tell the container runtime what command, inside the image to run when the container is created. These metadata fields are called Entrypoint and Command. For those users who are familiar with Dockerfile, the fields equate to the ENTRYPOINT and CMD commands. These two fields contain arrays of strings that are combined to create the command line that is used when you run your container.

For example, if your container image has an Entrypoint value of /myapp and a Command value of --debug, then the full command that is run is /myapp --debug (an array of two strings). Notice that because this action is a concatenation of two arrays, if Entrypoint is an empty array then the Command array's first array element is the executable that is run in your container.

When you create a Code Engine application or job, you can provide values for both the Entrypoint and Command arrays.



Docker and Code Engine names

 Description Docker name Code Engine name 

 The command that is run by the container. ENTRYPOINT command 
 The arguments that are passed to the command. CMD args 





* If --command is used, then any image Entrypoint value is overwritten and any image cmd values are ignored.
* If --argument is used, then any image Command value in overwritten.



To better understand this process, let's look at a few examples,



Images and Code Engine examples

 Image Entrypoint Image Cmd Code Engine command Code Engine args Command that is run 

 /myapp --debug <not set> <not set> /myapp --debug 
 /myapp --debug /myapp2 <not set> /myapp2 
 /myapp --debug <not set> -d /myapp -d 
 /myapp --debug /myapp2 -d /myapp2 -d
[Onboarding your Operator bundle](https://cloud.ibm.com/docs/sell?topic=sell-bundle-onboard)Onboarding your Operator bundle

This tutorial walks you through how to onboard a Certified Operator bundle from a Red Hat registry. By completing this tutorial, you learn how to import the Red Hat OpenShift on IBM Cloud Operator bundle, configure the deployment, license, and other details, and validate that the Operator bundle can be installed on a cluster.

Container Registry Selling on IBM Cloud



* 45 minutes
* 2023-03-31



[Onboarding your Operator](https://cloud.ibm.com/docs/sell?topic=sell-operator-onboard)Onboarding your Operator

This tutorial walks you through how to onboard a sample Node-RED Operator to your private catalog in IBM Cloud®. You can onboard an Operator or Operator bundle by using a TGZ file. By completing this tutorial, you learn how to import the Operator, configure the deployment, license, and other details, and validate that the Operator can be installed on a Red Hat OpenShift cluster.

Container Registry Selling on IBM Cloud



* 45 minutes
* 2023-03-31



[Onboarding your Terraform template](https://cloud.ibm.com/docs/sell?topic=sell-terraform-template-onboard)Onboarding your Terraform template

This tutorial walks you through how to onboard a Terraform template to your private catalog in IBM Cloud®.

Selling on IBM Cloud



* 45 minutes
* 2023-03-31



[Onboarding a virtual server image with Terraform to a private catalog](https://cloud.ibm.com/docs/sell?topic=sell-vsimage-onboard)Onboarding a virtual server image with Terraform to a private catalog

This tutorial walks you through how to onboard a virtual server image with Terraform to a private catalog. By completing this tutorial, you learn how to import the virtual server image from a GitHub repository, configure the deployment and other details, and validate that you can deploy the image to a target IBM Cloud® Virtual Private Cloud (VPC).
Create a local directory where you want to store the build context. The build context contains your Dockerfile and related build artifacts, such as the app code. Navigate to this directory in a command-line window.
2. Create a Dockerfile.



1. Create a Dockerfile in your local directory.

touch Dockerfile
2. Use a text editor to open the Dockerfile. At a minimum, you must add the base image to build your image from. Replace <source_image> and <tag> with the image repository and tag that you want to use. If you're using an image from another private registry, define the full path to the image in IBM Cloud Container Registry.

FROM <source_image>:<tag>

For example, to create a Dockerfile that is based on the public IBM WebSphere Application Server Liberty (ibm/liberty) image, use the following command.

FROM icr.io/ibm/liberty:latest
LABEL description="This is my test Dockerfile"
EXPOSE 9080

This example adds a label to the image metadata and exposes port 9080. For more Dockerfile instructions that you can use, see the [Dockerfile Reference](https://docs.docker.com/engine/reference/builder/).



3. Decide on a name for your image. The image name must be in the following format, where <my_namespace> is your namespace information, <repo_name> is the name of your repository, and <tag> is the version that you want to use for your image:

<region>.icr.io/<my_namespace>/<repo_name>:<tag>

To find your namespace, run the ibmcloud cr namespace-list command.
4. Take note of the path to the directory that contains your Dockerfile. If you run the commands in the following steps while your working directory is set to where your build context is stored, you can replace <directory> with a period (.).
5.
[Action icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg), and select Delete. When you delete a space, all included resources and users are also deleted.

You can delete spaces but not orgs.
* To repurpose an org, delete all spaces within the org and then rename it. Although you cannot delete orgs, you can simplify the list on the Cloud Foundry Orgs page by clearing and then re-using obsolete orgs rather than creating new ones.
* To edit user roles at the org level, click the Actions icon ![Action icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg), and select Users.

Depending on how you want to modify the user permissions, select or clear the checkbox for a specific role. The roles that you can assign at the organization level are Manager, Billing manager, and Auditor. For more information, see [Cloud Foundry roles](https://cloud.ibm.com/docs/account?topic=account-mngcfcfroles).
* To edit user roles for a specific space, click the org in which the space is assigned. Then, click the name of the space.

Depending on how you want to modify the user permissions, select or clear the checkbox for a specific role. The roles that you can assign at the space level are Manager, Developer, and Auditor. For more information, see [Cloud Foundry roles](https://cloud.ibm.com/docs/account?topic=account-mngcfcfroles).
* To manage your domains, click the Actions icon !
--job The name of the job to be run. This value is required if you do not specify the --name and --image values. 
 --array-indices Specifies the indices of the instances that are used to run the job. Specify the list or range of indices that are separated by hyphens (-) or commas (,); for example, 1,3,6,9 or 1-5,7-8,10. The maximum is 999999. This value is optional. The default value is 0. 



The JOB_INDEX environment variable is automatically injected into each instance of your job whenever the job is run. For more information about environment variables that are set by Code Engine, see [I see configmaps that I didn't create. Can I delete them?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-configmapinside-configmaps).





 Running a job with the CLI without first creating a job configuration 

With the CLI, you can submit a job run without first creating a job configuration. You can specify the same configuration options on the jobrun submit and jobrun resubmit commands that are available with the job create command.

For example, the following [ibmcloud ce jobrun submit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-create) command submits a job run to reference the us.icr.io/mynamespace/myhello_bld image by using the myregistry access information. Because this job run is not referencing a defined job configuration, you must specify values for the --name and image options. Use --name to specify the name of this job run and use --image to provide the name of the image that is used for this job run. The --array-indices option creates five new instances to run the container image. For job runs, the default value for cpu is 1 and the default value for memory is 4G. The resource limits and requests are applied per instance, so each instance gets 4 G memory and 1 vCPU.
The "docker-daemon" parameter is used when the image is present locally. The "docker" parameter is used when the image is present in a registry. In the skopeo copy example shown above, the image that is present locally is tagged with "xx.icr.io/yournamespace/hello-world:base_signed". It is signed and pushed to the destination "docker://xx.icr.io/yournamespace/hello-world:base_signed".





 Creating a registration definition file by using the CLI 

The registration definition file contains metadata about the OCI image you want to use for your Hyper Protect Virtual Server, such as the repository name and the credentials to pull the image. Because it can contain secret information, the file is automatically encrypted and signed by the CLI before you can use it to create a new Virtual Server. Use the following commands to create an encrypted registration definition file.

Before you call the hpvs registration-key-create command, gpg must be installed on your system.



1. To create a gpg registration key, run the hpvs registration-key-create command. The resulting output files are the required inputs for the hpvs registration-create command.

ibmcloud hpvs registration-key-create ID [--gpg-passphrase-path FILE-PATH] [-v VERBOSE]

Where:

ID
: Is the user ID to set for the gpg registration key.

--gpg-passphrase-path FILE-PATH
: Is the path for the file that contains the passphrase for the registration key. The passphrase must consist of at least 6 characters. To make sure that a new line is not appended, use echo with -n or cat with EOF. If the path is not specified, you are prompted for the passphrase.

-v, --verbose
: Set to true for verbose output.
2. To create a registration file, run the hpvs registration-create command.
Onboarding a virtual server image for Power Systems to a private catalog 

This tutorial walks you through how to onboard a public virtual server image for Power Systems Virtual Server to a private catalog. By completing this tutorial, you learn how to import the virtual server image from a GitHub repository, configure the deployment and other details, and validate that you can deploy the image to a target Power Systems Virtual Server instance.

This tutorial demonstrates how to onboard and publish a [sample virtual server image for Power Systems Virtual Server](https://github.com/IBM-Cloud/isv-power-vsi-product-deploy-sample) to IBM Cloud®. As you complete the tutorial, adapt each step to fit your product's needs.

This tutorial includes deploying the virtual server image to a target Power Systems Virtual Server. As a result, you will incur associated IBM Cloud infrastructure charges.



 Before you begin 



1. Create your Power Systems Virtual Server instance [and convert it into a public image](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-virtual-appliancesonboard-vsi).
2. After your image is converted into a public image, create your [Terraform template](https://cloud.ibm.com/docs/schematics?topic=schematics-create-tf-config).

Use the [latest release of the sample code](https://github.com/IBM-Cloud/isv-power-vsi-product-deploy-sample) as an example of how to set up your repository.
3. Make sure you're assigned the IBM Cloud Identity and Access Management (IAM) editor role on the Catalog Management and Partner Center - Sell services. See [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-services) for more information.
4.
Enter the required information in the following fields:



* Property: sslConnection
* Value: true



Click the Add button. Select the Database Connection tab.
5. Test the connection by clicking the Test Connection button. If the connection is successful, click OK.









 InfoSphere Data Architect 

These instructions explain how to create a connection from InfoSphere® Data Architect to a Db2 on Cloud database.



 Prerequisites 

Before attempting to connect to your Db2 on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2onCloud/connecting?topic=Db2onCloud-connect_ovprereqs).





 Procedure 



1. In the Data Source Explorer view of InfoSphere Data Architect, right-click Database Connections, then select New.
2. On the Local tab, select DB2 for Linux, UNIX, and Windows as the database manager.
3. On the General tab, enter the following values:



* Database: BLUDB
* Host: The host name that you collected beforehand.
* Port: For a connection without SSL, enter 50000. For a connection with SSL, enter 50001.
* User name: The user ID that you collected beforehand.
* Password: The password that you collected beforehand.



4. For an SSL connection, click the Optional tab. Enter an sslConnection property and specify a value of true. Click Add.
5. (Optional): Click Test Connection to verify that the connection succeeded.









 CLPPlus 

Command line processor plus (CLPPlus) is included in the Db2 driver package. CLPPlus provides a command-line interface that you can use to connect to a Db2 on Cloud database. You can use CLPPlus to define, edit, and run statements, scripts, and commands.



 Prerequisites
Preparing a custom image for import 

Before you can upload your image to IBM Cloud Object Storage, you must first create the image. After the image is created and uploaded to IBM Cloud Object Storage, then you can [Import your custom image into VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-importing-custom-images-vpc).

Use one of the following procedures to create a custom image.



*  [Creating a Linux custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-linux-custom-image)
*  [Creating a Windows custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-windows-custom-image)
*  [Migrating a virtual server from the classic infrastructure](https://cloud.ibm.com/docs/vpc?topic=vpc-migrate-vsi-to-vpc)
*  [Creating a z/OS Wazi aaS custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-zos-custom-image)



Did you know that you can use the IBM Cloud® [Packer plug-in](https://github.com/IBM/packer-plugin-ibmcloud) to create and manage custom images on IBM Cloud®? For more information, see this [blog post](https://www.ibm.com/cloud/blog/build-hardened-and-pre-configured-vpc-custom-images-with-packer) for an example of how to use the IBM Cloud® plug-in for Packer.
Enter the required information in the following fields:



* Property: sslConnection
* Value: true



Click the Add button. Select the Database Connection tab.
5. Test the connection by clicking the Test Connection button. If the connection is successful, click OK.









 InfoSphere Data Architect 

These instructions explain how to create a connection from InfoSphere® Data Architect to a Db2 Warehouse on Cloud database.



 Prerequisites 

Before attempting to connect to your Db2 Warehouse on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-connect_ovprereqs).





 Procedure 



1. In the Data Source Explorer view of InfoSphere Data Architect, right-click Database Connections, then select New.
2. On the Local tab, select DB2 for Linux, UNIX, and Windows as the database manager.
3. On the General tab, enter the following values:



* Database: BLUDB
* Host: The host name that you collected beforehand.
* Port: For a connection without SSL, enter 50000. For a connection with SSL, enter 50001.
* User name: The user ID that you collected beforehand.
* Password: The password that you collected beforehand.



4. For an SSL connection, click the Optional tab. Enter an sslConnection property and specify a value of true. Click Add.
5. (Optional): Click Test Connection to verify that the connection succeeded.









 CLPPlus 

Command line processor plus (CLPPlus) is included in the Db2 driver package. CLPPlus provides a command-line interface that you can use to connect to a Db2 Warehouse on Cloud database. You can use CLPPlus to define, edit, and run statements, scripts, and commands.



 Prerequisites
You can view job logs after you add logging capabilities. For more information, see [viewing job logs from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-joblogs-ui).





 Step 4: Updating a job 

You can manage your job by fine tuning your job configuration, which includes updating the code container image, code arguments or commands, runtime instance resources, or environment variables.

When the job is in ready state, you can update the job. Let's update the job that you created previously to change the container image from icr.io/codeengine/firstjob to icr.io/codeengine/testjob and then subsequently update an environment variable. When a request is sent to this icr.io/codeengine/testjob sample job, the job reads the environment variable TARGET and prints "Hello ${TARGET}!". If this environment variable is empty, "Hello World!" is returned. For more information about the code that is used for this example, see [testjob](https://github.com/IBM/CodeEngine/tree/main/testjob).



1. Navigate to your job page.



* From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), click the name of your project. Click Jobs to open a listing of your jobs.
* From the Jobs page, click the name of the job that you want to update.



2. To update the image reference of your job, provide the name of your image or configure an image. Update the name of the image from icr.io/codeengine/firstjob to icr.io/codeengine/testjob. Click Save.
3. Click Submit job.
4. From the Submit job pane, review and optionally change default configuration values such as instances, CPU, memory, number of job retries, and job timeout. You can specify either Number of instances or Array indices for the number of parallel job instances to run.
[The architecture of using recovery crypto units to initialize service instances](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/hs-crypto//images/minimum-touch-architecture.svg)

Figure 2. Initializing service instances by using recovery crypto units

The following sections explain each component in detail.



 Understanding IBM Cloud TKE CLI plug-in 

The TKE CLI plug-in is an addition to the IBM Cloud command-line interface (CLI). With the TKE CLI plug-in, you can send commands to the crypto units in your service instance to load the master key. The TKE CLI plug-in supports two approaches for loading the master key.

If your service instance has recovery crypto units, you can load the master key by running the ibmcloud tke auto-init command. This command guides you through steps to add administrators and set the signature thresholds, and then generates a random master key value in one of the recovery crypto units in your service instance and copies the value to the other crypto units. For more information about this approach, see [Initializing service instances by using recovery crypto units](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unit).

You can also use the TKE CLI plug-in to load the master key using key parts stored in key part files. This approach can be taken regardless of whether your service instance has any recovery crypto units. Using this approach, you run a series of commands to generate signature keys and master key parts, add administrators, set the signature thresholds, and load the master key registers. For more information, see [Initializing service instances by using key part files](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm).

You need to be assigned the appropriate role to perform TKE CLI plug-in operations.