vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To retrieve the location ID or name, run ibmcloud sat location ls.

--subdomain SUBDOMAIN
: Required. Enter the ID or name of the subdomain that you want to retrieve DNS record for. To list existing subdomains, run ibmcloud sat location dns ls.

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

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





 Example 

ibmcloud sat location dns get --location aaaaaaaa1111a1aaaa11a --subdomain s1b9782f9f75feeb8a5a4-d683ff82e51c94176a53d







 ibmcloud sat location dns ls 

List the DNS record for your location.

ibmcloud sat location dns ls --location LOCATION [--output json] [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Location resource in the Satellite location. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--location LOCATION
: Required. Enter the ID or name of the location that you want to show the DNS record for. To retrieve the location ID or name, run ibmcloud sat location ls.

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

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





 Example 

ibmcloud sat location dns ls --location aaaaaaaa1111a1aaaa11a







 ibmcloud sat location dns register 

Create a DNS record for your location and register the public or private IP addresses of your compute hosts that you added to the Satellite control plane to enable load balancing and health checking of your location.
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/containers?topic=containers-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 ks ingress domain rm --cluster CLUSTER --domain DOMAIN [-f] [-q]







 ibmcloud ks 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 ks 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 ks ingress domain secret regenerate --cluster mycluster --domain exampledomain [--output OUTPUT] [-q]







 ibmcloud ks ingress domain secret rm 

Delete the secret for an Ingress domain and prevent future renewal of the certificate.

ibmcloud ks ingress domain secret rm --cluster CLUSTER --domain DOMAIN [-f] [--output OUTPUT] [-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.
14 December 2020 



 New resources New data sources Enhancements 

 <br><br> * [ibm_cis_routing](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_routing)<br> * [ibm_cis_cache_settings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_cache_settings)<br> * [ibm_cis_custom_page](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_custom_page)<br> * [ibm_dns_glb](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/dns_glb)<br> * [ibm_dns_glb_monitor](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/dns_glb_monitor)<br> * [ibm_dns_glb_pool](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/dns_glb_pool)<br> * [ibm_is_vpc_routing_table](
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/cli?topic=cli-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 ks ingress domain rm --cluster CLUSTER --domain DOMAIN [-f] [-q]







 ibmcloud ks 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 ks 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 ks ingress domain secret regenerate --cluster mycluster --domain exampledomain [--output OUTPUT] [-q]







 ibmcloud ks ingress domain secret rm 

Delete the secret for an Ingress domain and prevent future renewal of the certificate.

ibmcloud ks ingress domain secret rm --cluster CLUSTER --domain DOMAIN [-f] [--output OUTPUT] [-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.
Delete policy ID bdf62c30-35dd-4852-bcb8-2f0dd3929701 from my-profile without confirmation:

ibmcloud iam trusted-profile-policy-delete my-profile bdf62c30-35dd-4852-bcb8-2f0dd3929701 -f







 ibmcloud iam trusted-profile-link-create 

Create a link to a compute resource for a trusted profile

ibmcloud iam trusted-profile-link-create (NAME|ID) --name LINK_NAME --cr-type CR_TYPE --link-crn CRN [--link-namespace NAMESPACE --link-name NAME] [--output FORMAT] [-q, --quiet] [-f, --force]



 Command options 

NAME|ID (required)
: Name or ID of the profile to link the compute resource to.

--name
: Name for the link.

--cr-type (required)
: The compute resource type. VSI for Virtual Service Instance on VPC, IKS_SA for Service Accounts on Kubernetes clusters, or ROKS_SA for managed Red Hat OpenShift.

--link-crn (required)
: CRN of the VSI instance / cluster instance.

--link-namespace
: Namespace of the service account for IKS_SA or ROKS_SA, required if IKS_SA or ROKS_SA.

--link-name
: Name of the service account for IKS_SA or ROKS_SA, required if IKS_SA or ROKS_SA.

--output FORMAT
: Specify output format. Only 'JSON' is supported.

-f, --force
: Force failure if multiple profiles are found.

-q, --quiet
: Suppress verbose output.





 Examples 

Create link named my_link for trusted profile my-profile for an IKS_SA compute resource with service account name default, default namespace, and my_compute_resource_crn CRN:
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. Create a file that contains the complete JSON copied from there or at least what's in the following example. You can also [set HMAC credentials as environment variables](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-mainuhc-setting-hmac-credentials) and omit this command option.

An example of HMAC credentials:

{
"cos_hmac_keys": {
"access_key_id": "abc",
"secret_access_key": "xyz"
}
}

--cos-endpoint value
: Endpoint of IBM Cloud Object Storage (required). In the IBM Cloud Object Storage web UI, select your bucket and you can find Endpoints in the Configuration tab. Only public endpoints are supported for now. Support for private endpoints will come soon.

--cos-bucket-crn value
: IBM Cloud Object Storage bucket CRN (required). In the IBM Cloud Object Storage web UI, select your bucket and you can find Bucket instance CRN in the Configurations tab.

--cos-backup-file value
: The name of the backup file to be restored (required). The backup file name identifies the date and time yyyy-mm-dd-hhmmssZ (UTC) when the backup was generated. You can get a list of COS backup files in either of the following ways.



1. Using the UI.
Using --db, you can indicate the database that your keys are copied from, which is the database that they recopied into in your new Databases for Redis deployment. The --flush flag flushes the destination database before importing the keys from the source database. If you want to keep things fresh in your new Databases for Redis deployment, flush will delete all the keys first then import the new keys from your source database.

Running the aformentioned script that uses OldDB as the source for the data migration and NewDB as the destination for the migrated data, you get something like:

python pymigration.py OldDB.databases.appdomain.cloud OldDBpassword1 88888 NewDB.databases.appdomain.cloud NewDBpassword1 99999 /NewDBCA --sslsrc --ssldst 10000000 keys: 100% || Time: 0:00:00 Keys disappeared on source during scan: 0 Keys already existing on destination: 0

As you can see from the results, you copied 10 million keys from OldDB to NewDB. No keys were deleted on the OldDB database. If you add a new key to the OldDB deployment and attempt to migrate the data again, you’ll see that the Keys already existing on the destination changes to 10000000 since the original 10 million keys already exist on that database.

10000000 keys: 100% || Time: 0:00:00
Keys disappeared on source during scan: 0
Keys already existing on destination: 10000000







 Next steps 

After your data migration, all you need to do is swap out your application’s database connection strings with your new Databases for Redis connection string and credentials. That’s all it takes!
Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--nlb-subdomain SUBDOMAIN
: The subdomain to regenerate the secret for. To list subdomains, run ibmcloud oc nlb-dns ls --cluster CLUSTER.

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

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



 Example nlb-dns secret regenerate command 

ibmcloud oc nlb-dns secret regenerate --cluster mycluster --nlb-subdomain mycluster-a1b2cdef345678g9hi012j3kl4567890-0001.us-south.containers.appdomain.cloud







 Experimental: ibmcloud oc nlb-dns secret rm 

Virtual Private Cloud

Classic infrastructure

Delete a secret from an NLB subdomain and prevent future renewal of the certificate.

You might delete the secret for an NLB subdomain if you no longer use the subdomain, or if the owner of the secret leaves your organization.

ibmcloud oc nlb-dns secret rm --cluster CLUSTER --nlb-subdomain SUBDOMAIN [-f] [--output json] [-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.

--nlb-subdomain SUBDOMAIN
: The subdomain to delete the secret for. To list subdomains, run ibmcloud oc nlb-dns ls --cluster CLUSTER.

-f
: Optional: Force the command to run with no user prompts.

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

-q
: Optional: Do not show the message of the day or update reminders.
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-rules" "> --><-- <section "id="section-command-examples-page-rules" "> --> Examples List all page rules in domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis page-rules 31984fea73a15b45779fa0df4ef62f9b -i cis-demo --output JSON
<-- </section "id="section-command-examples-page-rules" "> --><-- </section "id="section-page-rules" "> --><-- <section "id="section-page-rule" "> --> ibmcloud cis page-rule Get details of a page rule. ibmcloud cis page-rule DNS_DOMAIN_ID PAGE_RULE_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! ! ! !
<-- <section "id="section-command-options-page-rule" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.PAGE_RULE_ID: The ID of page rule. Required.-i, --instance: Instance name or ID. 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" "> --><-- <section "id="section-command-examples-page-rule" "> --> Examples Get details of page rule a5836c2a7ea72d2e225890caea70ae32.
Retrieving your instance ID 

You can target an individual IBM Cloud® DNS Services service instance for operations by including its unique identifier, or instance ID, in API requests to the service.



 Using the IBM Cloud console 

You can view the instance ID that is associated with your DNS Services service instance by navigating to your IBM Cloud resource list.



1. [Log in to the IBM Cloud console](https://cloud.ibm.com/).
2. Go to Menu > Resource List, and then click Services to browse a list of your cloud services.
3. Click the table row that describes your DNS Services service instance.
4. From the service details view, copy the GUID value. This GUID value represents the instance ID that uniquely identifies your DNS Services service instance.







 Using the CLI 

You can also retrieve the instance ID for your service instance by using the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).



1. Log in to IBM Cloud with the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).

ibmcloud login

If the login fails, run the ibmcloud login --sso command to try again. The --sso parameter is required when you log in with a federated ID. If this option is used, go to the link listed in the CLI output to generate a one-time passcode.
2. Select the account, region, and resource group that contain your provisioned instance of DNS Services.
3. Retrieve the Cloud Resource Name (CRN) that uniquely identifies your DNS Services service instance.

ibmcloud resource service-instance <instance_name> --id

Replace <instance_name> with the unique alias that you assigned to your DNS Services service instance. The following truncated example shows the CLI output.
Copy Database 

The IBM® Db2® on Cloud Copy Database feature gives you the ability to copy your existing database to a new instance or easily change plans and instance types.

The following examples are helpful use cases for using a copy of a database:



* Run analytics or reports.
* Make a fresh copy of your production database each morning to use for development purposes.
* Make a template database for an app, and make a copy of that template as your apps need it.
* Move from a single node instance to a HA instance or vice versa.
* Move between Standard or Enterprise Plans.



Because the copy instance creates a new instance and restores your existing backup, it’s important to keep the following in mind:



* Create a full backup of the data you want restored onto the copy. Any data written after the backup will not be moved across.
* When moving between plans or instance types, an outage will be required to point your apps to the new hostname and port.





 Prerequisites 

The Copy Database feature in the Db2 on Cloud service copies a database from one service instance to a new service instance. To use this feature, a backup of the current database must exist.





 Copying a running instance 



 Select a backup 

To copy your instance to a new service instance:



1. Select Administration from the left menu.
2. Select the Backups tab.
3. Select a backup to copy to a new instance.
4. Click Clone.



Zoom

![Select a backup to Copy](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/cloning_select.png)

Figure 1. Select a backup to copy to a new instance





 Creating the copy instance 

Enter information for the new copy instance:



1. Select the data center location for the new copy instance under Datacenter location.
2. Enter a name under Service name.
3. Select the resource group of the new instance under Resource group.
4.
<-- </section "id="section-list-security-event-examples" "> --><-- </section "id="section-list-security-event" "> --><-- </section "id="section-security-events" "> --><-- <section "id="section-tls" "> --> TLS Manipulate TLS by using the following tls commands.<-- <section "id="section-show-tls-setting" "> --> ibmcloud cis tls-settings Get TLS settings for a given domain. ibmcloud cis tls-settings DNS_DOMAIN_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-show-tls-setting-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.-i, --instance: Instance name or ID. 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-show-tls-setting-options" "> --><-- <section "id="section-show-tls-setting-examples" "> --> Examples Get TLS settings for domain 372e67954025e0ba6aaa6d586b9e0b60. ibmcloud cis tls-settings 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"
<-- </section "id="section-show-tls-setting-examples" "> --><-- </section "id="section-show-tls-setting" "> --><-- <section "id="section-update-tls-settings" "> --> ibmcloud cis tls-settings-update Update TLS settings for a given DNS domain.
You can restrict the ciphers used for your domain using the CIS CLI plugin to the IBM Cloud CLI. See the ciphers option on the [domain settings command](https://cloud.ibm.com/docs/cis?topic=cis-cis-clidomain-settings).



Table 2. Origin cipher suites

 OpenSSL Name TLS 1.0 TLS 1.1 TLS 1.2 TLS 1.3 

 AEAD-AES128-GCM-SHA256 <br><br>[1] ![Available](https://cloud.ibm.com/docs-content/v1/content/cb1eb27836421578019401fa7556779109430b29/icons/checkmark-icon.svg) 
 AEAD-AES256-GCM-SHA384 <br><br>[2] ![Available](https://cloud.ibm.com/docs-content/v1/content/cb1eb27836421578019401fa7556779109430b29/icons/checkmark-icon.svg) 
 AEAD-CHACHA20-POLY1305-SHA256 <br><br>[3] ![Available](https://cloud.ibm.com/docs-content/v1/content/cb1eb27836421578019401fa7556779109430b29/icons/checkmark-icon.svg) 
 ECDHE-ECDSA-AES128-GCM-SHA256 ![Available](https://cloud.ibm.com/docs-content/v1/content/cb1eb27836421578019401fa7556779109430b29/icons/checkmark-icon.svg) 
 ECDHE-RSA-AES128-GCM-SHA256 !
The following example shows you how to use the CLI to bring your own IP addresses for subnets in the 'us-south-1' and 'us-south-2' zones of your VPC.



1. Create an address prefix named my-first-prefix in the us-south-1 zone:

ibmcloud is vpc-address-prefix-create my-first-prefix $VPC us-south-1 172.16.0.0/23
2. Create an address prefix named another-prefix in the us-south-2 zone:

ibmcloud is vpc-address-prefix-create another-prefix $VPC us-south-2 172.16.2.0/23
3. Create a subnet named my-subnet within your new address prefix in the us-south-1 zone:

ibmcloud is subnet-create my-subnet $vpc us-south-1 --ipv4-cidr-block "172.16.0.0/25"
4. Create a subnet named another-subnet within your new address prefix in the us-south-2 zone:

ibmcloud is subnet-create another-subnet $vpc us-south-2 --ipv4-cidr-block "172.16.2.0/25"
DC should be your domain
 specify the password generated above for "olcRootPW" section
dn: olcDatabase={1}monitor,cn=config
changetype: modify
replace: olcAccess
olcAccess: {0}to * by dn.base="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth"
read by dn.base="cn=Manager,dc=ibmsymphony,dc=com" read by * none
dn: olcDatabase={2}hdb,cn=config
changetype: modify
replace: olcSuffix
olcSuffix: dc=ibmsymphony,dc=com
dn: olcDatabase={2}hdb,cn=config
changetype: modify
replace: olcRootDN
olcRootDN: cn=Manager,dc=ibmsymphony,dc=com
dn: olcDatabase={2}hdb,cn=config
changetype: modify
add: olcRootPW
olcRootPW: {SSHA}TVW9z6WLIBC3EXtFHFWnb2EVlK7EZQ3b
dn: olcDatabase={2}hdb,cn=config
changetype: modify
add: olcAccess
olcAccess: {0}to attrs=userPassword,shadowLastChange by
dn="cn=Manager,dc=ibmsymphony,dc=com" write by anonymous auth by self write by * none
olcAccess: {1}to dn.base="" by * read
olcAccess: {2}to * by dn="cn=Manager,dc=ibmsymphony,dc=com" write by * read
Show more

Replace the {SSHA} value with the password hash that you generated in the previous step.
9. Apply the changes by running the following command:
--sort-by, -s
: Specifies the column by which to sort the list. Valid values are name and age. This value is optional. The default value is name.





 Example 

The following example displays a listing of all custom domain mappings.

ibmcloud ce domainmapping list





 Example output 

Listing domain mappings...
OK

Name CNAME Target Target-Type Status Secret Name Age
www.example.com custom.abcdabcdabc.us-south.codeengine.appdomain.cloud myapp app ready mytlssecret 36m

To view a listing of all domain mappings for your applications, including both the custom domain mappings and any automatically generated system domain mappings, specify the --all option with the [ibmcloud ce domainmapping list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-domainmapping-list) command.







 ibmcloud ce domainmapping update 

Update a custom domain mapping.

ibmcloud ce domainmapping update --domain-name DOMAIN_NAME --target TARGET_NAME --tls-secret <tls-secret-name> [--quiet]



 Command Options 

--domain-name, --dn, -n, --name
: The name of the domain mapping. This value is required.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--target, -t
: The name of the target application. This value is optional.

--tls-secret, --secret, --tls
: Specify a TLS secret that contains the certificate including all its intermediate certificates and the corresponding private key for the domain mapping. The certificate must be signed by a trusted, public certificate authority (CA). Self-signed certificates are not supported. This value is optional.





 Example 

The following example updates the www.example.com domain mapping to use mytlssecret2 instead of mytlssecret.