vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Option Description 

 --name The name of the job to bind. This value is required. 
 --service-instance Specify the name of an existing service instance to bind to the job. This value is required. 
 --service-credential The name of the existing service credential to bind. 



4. Verify that the credentials were generated by using the application get, the job get, or the function get command. In the following example, verify that the credentials that were created in the previous example were created.

ibmcloud ce job get --name myjob

Example output

[...]
Service Bindings:
Name ID Service Instance Service Type Role / Credential Environment Variable Prefix
myjob-ce-service-binding-abcde abcde645-d3f9-407d-b964-6c3ae69abcde my-object-storage cloud-object-storage my-cos-credential CLOUD_OBJECT_STORAGE
[...]









 Unbinding service instances 

Unbinding service instances from an app, job, or function workloads removes existing service bindings.

When you unbind (or remove) a service binding, you are deleting the association of the app, job, or function workload with the service access secret such that the workload no longer has access to previously bound IBM Cloud service.

After a service binding is defined between your application and a service instance, the service binding is active as long as the application and the service instance is active, or you haven't completed an unbind operation to remove the service binding. If the service instance is deleted, you'll need to manually delete the service binding.



 Unbinding a service instance from the console 



1. From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), go to your project.
2. From the Overview page, click Service bindings to view a listing of all defined service bindings. Or, if you want to manage service bindings from the context of your app or job, from the Overview page, click Applications or Jobs and click the name of your app or job.
* [Initializing service instances](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unitinitialize-hsm-recovery-crypto-unit-steps)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unitinitialize-hsm-recovery-crypto-unit-whats-next)



[Initializing service instances using key part files](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsminitialize-hsm)



* [Before you begin](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsminitialize-hsm-cli-prerequisite)
* [Selecting target crypto units for service initialization](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsmidentify_crypto_units)
* [Loading master keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsmload-master-keys)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsminitialize-crypto-cli-next)



[Using a signing service to manage signature keys for instance initialization](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-signing-service-signature-keysigning-service-signature-key)



* [Signing service prerequisites](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-signing-service-signature-keysigning-service-requirements)
See the [application create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) and the [job create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-create) commands.

Want to learn more about applications and jobs? See [Working with apps in Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloads) and [Working with jobs and jobruns](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-plan).





 Clean up 

After you finish this tutorial, you can clean up the resources that you created with the following commands.

Delete your application

ibmcloud ce app delete --name myapp

When you delete your app, the associated build files are also deleted.

Lastly, delete the images that the build created from IBM Cloud Container Registry.



1. Navigate to [Registry](https://cloud.ibm.com/registry/start) in the IBM Cloud console.
2. Find the archive and the image that are associated with your application by searching for your application name.
3. Select the archive and image and delete.







 Next steps 



1. Just starting your migration? Check out [Getting started](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-getstart).
2. [Compare Cloud Foundry terminology with Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-terms).
3. Deploying Cloud Foundry applications in Code Engine: Getting started (current page)
4. Does your application use service bindings? Check out [Migrating your service bindings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-bind).
* [Updating the minor version of the Istio add-on](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_minor)
* [Updating the istioctl client and sidecars](https://cloud.ibm.com/docs/containers?topic=containers-istioupdate_client_sidecar)



* [Uninstalling Istio](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_uninstall)



* [Step 1: Managing resources before uninstallation](https://cloud.ibm.com/docs/containers?topic=containers-istiouninstall_resources)
* [Step 2: Uninstalling the Istio add-on](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_uninstall_addon)
* [Step 3: Remove the Istio operator](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_uninstall_operator)
* [Uninstalling other Istio installations in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_uninstall_other)



* [Troubleshooting](https://cloud.ibm.com/docs/containers?topic=containers-istioistio-ts)



[Managing and exposing apps in the service mesh](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshistio-mesh)



* [Understanding the BookInfo sample app](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshistio_bookinfo)
* [Setting up the BookInfo sample app](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshbookinfo_setup)
Use the [UI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=clifs-remove-replication-ui), [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=clifs-remove-replication-cli), or [API](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=clifs-remove-replication-api) to remove the replication relationship. You can also specify that the source and replica file shares are split if a [failover](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-failover) operation does not succeed.

Removing the replication relationship cannot occur when another operation is being performed on the source or replica file share (for example, the file share size is being expanded). The split operation remains pending until the other operation completes.

When you remove the replication relationship, you can't undo the action. Also, the data on the replica is not synced automatically with the source file before removal of the replication relationship.



 Remove the replication relationship in the UI 

To remove the replication relationship in the UI:



1. Navigate to the list of all file shares. From the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > File Shares.
2. Click the name of a file share or replica file share to go to its details page.
3. In the File share replication relationship section, click Remove replication relationship. Removing the replication relationship creates two independent file shares.
4. In the new window, click Unlink. The data on the replica is not synced with the source file share automatically before the replication relationship is removed.



The file share details page indicates no replication relationship.
const pipelineSvc = CdTektonPipelineV2.newInstance();
const params = {
id: {pipeline_id},
};
const res = await pipelineSvc.deleteTektonPipeline(params);
})();

from ibm_continuous_delivery.cd_tekton_pipeline_v2 import CdTektonPipelineV2
...
pipeline_service = CdTektonPipelineV2.new_instance()
response = pipeline_service.delete_tekton_pipeline(
id={pipeline_id}
)

import {
"github.com/IBM/continuous-delivery-go-sdk/cdtektonpipelinev2"
}
...
cdTektonPipelineOptions := &cdtektonpipelinev2.CdTektonPipelineV2Options{}
pipelineSvc, err = cdtektonpipelinev2.NewCdTektonPipelineV2UsingExternalConfig(cdTektonPipelineOptions)
deleteTektonPipelineOptions := pipelineSvc.NewDeleteTektonPipelineOptions(
{pipeline_id}
)
response, err := pipelineSvc.DeleteTektonPipeline(deleteTektonPipelineOptions)



The following table lists and describes each of the variables that are used in the previous step.



Table 5. Variables for deleting the Delivery Pipeline with the API

 Variable Description 

 {region} The region in which the toolchain resides, for example, us-south. 
 {toolchain_id} The ID of the toolchain that contains the pipeline to delete. 
 {pipeline_id} The ID of the pipeline that you want to delete. 
 {iam_token} A valid IAM bearer token. 







 Deleting a Delivery Pipeline with Terraform 



1. Locate the Terraform file (for example, main.tf) that contains the resource block for the existing pipeline.

The resource in the following example describes an existing pipeline.
deleteDatabaseOptions := service.NewDeleteDatabaseOptions(
"<db-name>",
)

ok, response, err := service.DeleteDatabase(deleteDatabaseOptions)
if err != nil {
panic(err)
}

b, _ := json.MarshalIndent(ok, "", " ")
fmt.Println(string(b))

import { CloudantV1 } from '@ibm-cloud/cloudant';

const service = CloudantV1.newInstance({});

service.deleteDatabase({db: '<db-name>'}).then(response => {
console.log(response.result);
});

The previous Go example requires the following import block:

import (
"encoding/json"
"fmt"
"github.com/IBM/cloudant-go-sdk/cloudantv1"
)

All Go examples require the service object to be initialized. For more information, see the API documentation's [Authentication section](https://cloud.ibm.com/apidocs/cloudant?code=goauthentication-with-external-configuration) for examples.

If deletion succeeds, you get a 200 or 202 response. An error response uses the HTTP status code to indicate what went wrong.



Table 1. HTTP status codes

 Code Description 

 200 Database deleted successfully. 
 202 Database was successfully deleted on some nodes, but the number of nodes is less than the write quorum. 
 404 Database does not exist on all of the nodes. 



See the following example response that is received after a database is deleted successfully:

{
"ok": true
}
SC-21 - Secure Name / Address Resolution Service (recursive or Caching Resolver) 



  Control requirements 

SC-21 - 0
:   The information system requests and performs data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources.





  NIST supplemental guidance 

Each client of name resolution services either performs this validation on its own, or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching domain name system (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to enable clients to verify the authenticity and integrity of response data.
Disabling recursion for DNS 

IBM Cloud® DNS servers perform recursion by default. Recursion allows your DNS server to contact other DNS servers to assist in resolving domain names when it cannot resolve the domain itself. Recursion can prove to be useful when necessary; however, it also opens the DNS server open to attack, which could take down the DNS server altogether. System administrators generally identify a need for recursion and act accordingly. Otherwise, it is best to disable recursion. Follow these steps based on your operating system or control panel to disable DNS recursion.



  Disable recursion in Plesk 



1.  Log in to the Plesk Admin Panel.
2.  Select Tools and Settings.
3.  Click DNS Template Settings from the section.
4.  Select Localnets from the DNS Recursion section.
5.  Click the OK button.







  Disable recursion in Windows Server 2003 and 2008 



1.  Open DNS Manager from the Start menu by clicking Start > Administrative Tools > DNS.
2.  Right-click on the DNS Server in the Console Tree.
3.  Select the Properties tab.
4.  Click the Advanced button in the Server Options section.
5.  Select the Disable Recursion checkbox.
6.  Click the OK button.







  Disable recursion in Linux 



1.  Locate the BIND configuration file within the operating system. The BIND configuration file is usually located in one of the following paths:



*  /etc/bind/named.conf
*  /etc/named.conf



2.  Open the named.conf file in your preferred editor.
3.  Add the following parameters to the Options section:



*  allow-transfer {"none";};
*  allow-recursion {"none";};
*  recursion no;



4.  Restart the device.
To find the resource name or CRN, use the IBM Cloud command ibmcloud resource service-instances --long.

--output value
: Use the --output option with value json to format output in JSON.







 ibmcloud dbaas backup restore 

This command restores a backup from local storage or IBM Cloud Object Storage for a database cluster. To restore the backup into a new service instance, create a new service instance first.

Restore from local storage:

Local backups can only be restored into your current service instance.

ibmcloud dbaas backup restore RESOURCE_NAME --local-backup-id LOCAL_BACKUP_ID [--output json]

Restore from IBM Cloud Object Storage:

To restore the backup into a new service instance, create a new service instance first.

ibmcloud dbaas backup restore RESOURCE_NAME --cos-hmac-credentials-path CREDENTIALS_PATH --cos-endpoint COS_ENDPOINT --cos-bucket-crn BUCKET_CRN --cos-backup-file FILE_NAME [--output json]



 Command options 

RESOURCE_NAME
: The name or CRN of the target DBaaS service instance. To find the resource name or CRN, use the IBM Cloud command ibmcloud resource service-instances --long.

--output value
: Use the --output option with value json to format output in JSON.

Restore from local storage:

--local-backup-id value
: The ID of the local backup to be restored (required). You can use the [ibmcloud dbaas backup list](https://cloud.ibm.com/docs/cli?topic=cli-dbaas_cli_pluginbackup-list) command to get the list of local backups.

Restore from IBM Cloud Object Storage:

--cos-hmac-credentials-path value
: Path to the file that contains the HMAC credentials (access_key_id and secret_access_key) in JSON format. You can find the credentials by selecting Service credentials in the IBM Cloud Object Storage web UI.
Examples 

List all secondary zones for a custom resolver f1aba936b94213e5b8dca0c0dbf1f9cc.

ibmcloud dns secondary-zones f1aba936b94213e5b8dca0c0dbf1f9cc -i "dns-demo"







 ibmcloud dns secondary-zone-delete 

Delete a secondary zone.

ibmcloud dns secondary-zone-delete RESOLVER_ID SECONDARY_ZONE_ID [-i, --instance INSTANCE_NAME] [--output FORMAT]



 Command options 

RESOLVER_ID
: The ID of the custom resolver. Required.

SECONDARY_ZONE_ID
: The ID of the secondary zone. Required.

-i, --instance value
: Instance name or ID. If not set, the context instance specified by dns instance-target INSTANCE is used.

--output value
: Specify output format. Currently, json is the only supported format.





 Examples 

Delete a secondary zone e2aba136a93212e5a8dce0c2dbf6f2ee for a custom resolver f1aba936b94213e5b8dca0c0dbf1f9cc.

ibmcloud dns secondary-zone-delete f1aba936b94213e5b8dca0c0dbf1f9cc e2aba136a93212e5a8dce0c2dbf6f2ee -i "dns-demo"









 Cross-account access 

Manage cross accounts by using the following cross-account access commands.



 ibmcloud dns cross-account linked-zone-create 

Create a linked zone.

ibmcloud dns cross-account linked-zone-create --owner-instance-id OWNER_INSTANCE_ID --owner-zone-id OWNER_ZONE_ID [--label LABEL] [--description DESCRIPTION] [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

--owner-instance-id value
Updating zone 'example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae' for service instance 'DNS Services-km' ...
OK

ID example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae
Name example.com
Description example zone
Label us-south
State PENDING_NETWORK_ADD
Created On 2020-04-10 07:21:51.774444868 +0000 UTC
Modified On 2020-04-10 07:38:36.712131819 +0000 UTC





 Listing DNS zones 

Use the ibmcloud dns zones command to list all zones.

$ ibmcloud dns zones
Listing zones for service instance 'DNS Services-km' ...
OK

ID Name Status
example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae example.com PENDING_NETWORK_ADD





 Deleting a DNS zone 

Use the ibmcloud dns zone-delete followed by the zone ID to delete a zone.

ibmcloud dns zone-delete $DNS_ZONE_ID
Migrating Elasticsearch 

If you are a current user of Elasticsearch, use the [Snapshot/restore Elasticsearch API](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html) and the [S3 repository plug-in](https://www.elastic.co/guide/en/elasticsearch/plugins/current/repository-s3.html) to migrate your data into IBM Cloud® Databases for Elasticsearch.

Take a snapshot of your existing Elasticsearch, store the snapshot in an AWS S3 or IBM Cloud® Object Storage bucket and then restore the snapshot to your Databases for Elasticsearch deployment.

To migrate while data is still being written to your existing Elasticsearch, take multiple snapshots and perform multiple incremental restores. After the Databases for Elasticsearch deployment catches up to the state of your Elasticsearch, move your application writes to Databases for Elasticsearch.



 Requirements 

Ensure you meet the following requirements before migrating:



* Your existing Elasticsearch must have the [S3 repository plug-in](https://www.elastic.co/guide/en/elasticsearch/plugins/current/repository-s3.html).
* An Elasticsearch that is version 5.x or 6.x. Migration is possible between major versions, but the versions must have compatible indexes. Indexes that are made in Elasticsearch 2.x are not compatible with 6.x and need reindexing in 5.x before migration.
* A matching Databases for Elasticsearch deployment that has at least as many resources allocated to it your existing Elasticsearch. Also, ensure that the same [plug-ins](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-plugins) are available on Databases for Elasticsearch that you have on the existing Elasticsearch.
* Your our own S3 or IBM Cloud Object Storage repository.



Incremental restores work only if the number of shards of each index on both deployments match.
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-command-options-page-rule-create" "> --><-- <section "id="section-command-examples-page-rule-create" "> --> Examples Create a page rule for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis page-rule-create 31984fea73a15b45779fa0df4ef62f9b --json '{"targets":{"target":"url", "constraint":{"operator": "matches", "value":"example.com/images/"}}], "actions":{"id":"always_online", "value":"on"}] ! ! ! , "priority":1, "status": "active"}' cis-demo --output JSON
<-- </section "id="section-command-examples-page-rule-create" "> --><-- </section "id="section-page-rule-create" "> --><-- <section "id="section-page-rule-update" "> --> ibmcloud cis page-rule-update Update the page rule of the DNS domain. ibmcloud cis page-rule-update DNS_DOMAIN_ID PAGE_RULE_ID (--json @JSON_FILE | JSON_STRING) -i, --instance INSTANCE] --output FORMAT]
Deprecated] ibmcloud cis page-rule-update DNS_DOMAIN_ID PAGE_RULE_ID (-s, --json-str JSON_STR | -j, --json-file JSON_FILE) -i, --instance INSTANCE] --output FORMAT] ! !!!!!!
ibmcloud oc ingress domain rm --cluster CLUSTER --domain DOMAIN [-f] [-q]

Minimum required permissions
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster where the domain is applied.

--domain DOMAIN
: Required. The domain that you want to remove from the cluster. You cannot specify the default domain. If you want to remove the domain that is currently set as the default for your cluster, you must first [replace the default](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliingress-domain-default-replace) with another domain.

-f

-q
: Optional: Do not show the message of the day or update reminders.



 Example ingress domain rm command 

ibmcloud oc ingress domain rm --cluster CLUSTER --domain DOMAIN [-f] [-q]







 ibmcloud oc ingress domain secret regenerate 

Regenerate the certificate for an Ingress domain. Run this command to generate a new token in your DNS provider and apply it to your cluster

ibmcloud oc ingress domain secret regenerate --cluster CLUSTER --domain DOMAIN [--output OUTPUT] [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster where the domain is applied.

--domain DOMAIN
: Required. The domain you want to regenerate.

--output OUTPUT
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example ingress domain secret regenerate command 

ibmcloud oc ingress domain secret regenerate --cluster mycluster --domain exampledomain [--output OUTPUT] [-q]







 ibmcloud oc ingress domain secret rm
iaTr4UNYm5WtYTzMzqh8l1+MFFDl9xDBnvULuCIIrglM5MeS/qnSg1uMoH2oVPj9TVst/ir8CgYEAxrI7Ws9Zc4Bt70N1As+UnlySjaEVZCMkqvHJ6TCuVZFfQoE0r0whdLdRLU2PsLFP+q7qaeZQqgBaNSKeVcDYRn9B+nY/jOmQoPewPVsp/vQTCnE/R81spu0mp0YI6cIheT1Z9zAy322svcc43JaWB7nmEbeqyLOP4Z4qSOcmghZBSECgYACvR9Xs0DGn+wCsW4vze/2ei77MD4OQvepPIFXndFZtlBy5ADcgE9z0cuVB6CiL8DbdK5kwY9pGNr8HUCI03iHkW6Zs+0L0YmihfEVenPG19PSzK9CaDdhD9KFZSbLyVFmWfxOt50H7YRTTiPMgjyFpfi5j2q348yVT0tEQSnfhRqaQKBgAcWPokmJ7EbYQGeMbS7HC8eWO/RyamlnSffdCdSc7ue3zdVJxpAkQ8Wnqu80pEIF6raIQfAf8MXiiZ7auFOSnHQTXUbhCpvDLKi0Mwq3G8Pl07l+2s6dQG6Tnlv6XTQaMyf6n1yjzL+fzDrH3qXMxHMO/b13EePXpDMpY7HQpoLDin-----END RSA PRIVATE KEY-----n", "bundle_method": "compatible"}' -i "cis-demo"
Show more
<-- </section "id="section-update-cert-examples" "> --><-- </section "id="section-update-cert" "> --><-- <section "id="section-change-priority-custom-cert" "> --> ibmcloud cis certificate-priority-change Change custom certificates' priority for a given DNS domain.