vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Run curl -X GET https://schematics.cloud.ibm.com/v1/workspaces -H "Authorization: <iam_token>" to list and select the workspace ID that you want to delete. For more information about listing the workspace, see [Schematics Workspaces list](https://cloud.ibm.com/apidocs/schematics/schematicslist-workspaces) API.
3. Run curl -X DELETE https://schematics.cloud.ibm.com/v1/workspaces/{id} -H "Authorization: <iam_token>" to delete the workspace. For more information about workspace delete, see [Schematics Workspaces delete](https://cloud.ibm.com/apidocs/schematics/schematicsdelete-workspace) API.







 Actions 

You can follow these steps to delete the Schematics objects.



1. [Set up your REST client](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-api&interface=apics_api) to execute Schematics API.
2. Run curl --location --request GET https://schematics.cloud.ibm.com/v2/actions/actions --header "Authorization: <access_token>" to list and select an action ID that you want to delete. For more information about listing the actions, see [Schematics Actions list](https://cloud.ibm.com/apidocs/schematics/schematicslist-actions) API.
3. Run curl --location --request DELETE https://schematics.cloud.ibm.com/v2/actions/{action_id} --header "Authorization: <access_token> " to delete an action. For more information about Schematics Actions delete, see [Schematics Actions delete](https://cloud.ibm.com/apidocs/schematics/schematicsdelete-action) API.







 Inventories
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-list-security-event-options" "> --><-- <section "id="section-list-security-event-examples" "> --> Examples Get security events for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis security-events 31984fea73a15b45779fa0df4ef62f9b --action challenge --colo SJC --country US --host "www.example.com" --ip-class clean
--method POST --ray-id 187d944c61940c77 --cursor "6yDGxLKVeeHZZmORS_8XeSuhz9SjIJRaSa2lnsF01tQOHrfTGAP3R5X1Kv5iVUuMbNKhWNAXHOl6ePB0TUL8nw" -i "cis-demo"
<-- </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.
10. List the physical storage instance that your PV pointed to and note the id of the physical storage instance.

ibmcloud is volumes | grep <pv_name>
11. Remove the physical storage instance.

ibmcloud is volume-delete <vpc_block_id>
12. Verify that the physical storage instance is removed.

The deletion process might take up to 72 hours to complete.

ibmcloud is volumes
Deleting your deployment and removing your data 

IBM® Netezza® Performance Server for IBM Cloud Pak® for Data as a Service instances are deleted in production whenever you delete the instance in IBM Cloud.



  Deleting instances 

To delete your deployment instance:



1.  Log in to your IBM Cloud account.
2.  From the Resource list, select your deployment.
3.  Using the menu icon, choose Delete from the list.
Verify the assignment was created by listing your assignments.

curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignments" -H "accept: application/json" -H "Authorization: Bearer TOKEN"







 Removing Compute Engine storage from your apps 

If you no longer need your Google Compute Engine configuration, you can remove your apps, PVCs, PVs, and assignment from your clusters.



1. List your PVCs and note the name of the PVC that you want to remove.

oc get pvc
2. Remove any pods that mount the PVC. List all the pods that currently mount the PVC that you want to delete. If no pods are returned, you do not have any pods that currently use your PVC.

oc get pods --all-namespaces -o=jsonpath='{range .items[]}{"n"}{.metadata.name}{":t"}{range .spec.volumes[]}{.persistentVolumeClaim.claimName}{" "}{end}{end}' | grep "<pvc_name>"

Example output

app sat-gce-block-platinum
3. Remove the pod that uses the PVC. If the pod is part of a deployment or statefulset, remove the deployment or statefulset.

oc delete pod <pod_name>

oc delete deployment <deployment_name>

oc delete statefulset <statefulset_name>
4. Verify that the pod, deployment, or statefulset is removed.

oc get pods

oc get deployments

oc get statefulset
5. Delete the PVC.

oc delete pvc <pvc_name>
6. Verify that your PV is automatically removed.

oc get pv







 Removing the Compute Engine storage configuration from your cluster 

If you no longer plan on using your persistent disk storage in your cluster, you can use the CLI unassign your cluster from the storage configuration.
If the delete operation failed from the console or you want to use command line, you can use the oc command-line interface to complete the steps to uninstall. When you use the command line, you need to remove the resources on your OpenShift Container Platform cluster that are associated with IBM Cloud Pak for Multicloud Management.

If the OpenShift CLI is not installed, download and install the CLI from the Red Hat Customer Portal.

When you are running the commands to remove the associated resources, use the project that you selected during the installation of your OpenShift Container Platform cluster. Replace the <project_name> parameter in the following commands with your project name.



1. Download the uninstall.sh script from [github](https://github.com/IBM/cp4mcm-samples/blob/master/scripts/uninstall.sh). Run:



curl [https://raw.githubusercontent.com/IBM/cp4mcm-samples/master/scripts/cp4mcm-cleanup-utility.sh](https://raw.githubusercontent.com/IBM/cp4mcm-samples/master/scripts/cp4mcm-cleanup-utility.sh) -o uninstall.sh

2. Identify the path to the kubeconfig file for your cluster, for example: /root/.kube/config
3. Change the file permissions on the uninstall.sh script so you can run it:
 {: codeblock}
chmod 700 uninstall.sh



4. Run the uninstall.sh script as follows:



./uninstall.sh --mode uninstallEverything --kubeconfigPath /.kube/config --cloudpakNamespace <project_name>

5. Verify that IBM Cloud Pak for Multicloud Management is uninstalled by accessing the OpenShift web console and verifying that the IBM Cloud Pak for Multicloud Management components such as the pods and resources are no longer available.

 Troubleshooting
Create a dns record in domain 31984fea73a15b45779fa0df4ef62f9b.

ibmcloud cis dns-record-create 31984fea73a15b45779fa0df4ef62f9b --json '{"name": "testCNAME", "type": "CNAME", "content": "example.com"}' -i "cis-demo"
ibmcloud cis dns-record-create 31984fea73a15b45779fa0df4ef62f9b --type A --name testA --content "127.0.0.1" -i "cis-demo"







 ibmcloud cis dns-record-update 

Update a DNS record for a given domain of a service instance.

ibmcloud cis dns-record-update DNS_DOMAIN_ID DNS_RECORD_ID (--json @JSON_FILE | JSON_STRING) [-i, --instance INSTANCE] [--output FORMAT]
ibmcloud cis dns-record-update DNS_DOMAIN_ID DNS_RECORD_ID [--type TYPE] [--name NAME] [--content CONTENT] [--proxied PROXIED] [--ttl TTL] [--output FORMAT]
[Deprecated] ibmcloud cis dns-record-update DNS_DOMAIN_ID DNS_RECORD_ID --json-str JSON_STR [-i, --instance INSTANCE] [--output FORMAT]
[Deprecated] ibmcloud cis dns-record-update DNS_DOMAIN_ID DNS_RECORD_ID --json-file JSON_FILE [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

DNS_RECORD_ID
: The ID of DNS record. Required.

--name
: DNS record name.

--type
: DNS record type.
[Deprecated] ibmcloud cis dns-record-create DNS_DOMAIN_ID --json-file JSON_FILE [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

--name
: DNS record name.

--type
: DNS record type.

--content
: DNS record content.

--ttl
: Time to live for DNS record. Value of 1 is automatic. The default value is 1.

--proxied
: Control whether or not traffic should flow through the security and performance functions on CIS. CIS only proxies traffic for A, AAAA, and CNAME records. Valid values: true, false.

--json
: The JSON file or JSON string used to describe a DNS Record. Supported DNS Record types are: A, AAAA, CNAME, NS, TXT, MX, LOC, SRV, CAA, PTR.



* For type A, AAAA, CNAME, NS, TXT:



* The required fields in JSON data are name, type, content.
* The optional fields are ttl, proxied:



* proxied Control whether traffic should flow through the security and performance functions on CIS. CIS only proxies traffic for A,AAAA, and CNAME records.







Sample JSON data:

{
"name": "testA",
"type": "A",
"content": "127.0.0.1",
"proxied": true
}

{
"name": "testAAAA",
"type": "AAAA",
"content": "2001:0db8:0012:0001:3c5e:7354:0000:5db1",
"proxied": false
}

{
"name": "testCNAME",
"type": "CNAME",
When you add a domain to CIS, we give you a couple of name servers to configure at your registrar (or at your DNS provider, if you are adding a subdomain). The domain or subdomain remains in pending state until you configure the name servers correctly. Make sure you add both the name servers to your registrar or DNS provider. We periodically scan the public DNS system to check whether the name servers have been configured as instructed. As soon as we are able to verify the name server change (which can take up to 24 hours), we activate your domain. You can submit a request to recheck name servers by clicking on Recheck name servers in the overview page.





 Who is the registrar for my domain? 

Consult [https://whois.icann.org/](https://whois.icann.org/) for this information.

You must have the administrator privilege to edit your domain's configuration at the registrar in order to update or add the name servers provided for your domain when you add it to CIS. If you don't know who the registrar is for the domain you're trying to add to CIS, it is unlikely you have the permission to update your domain's configuration at the registrar. Work with the owner of the domain in your organization to make the necessary changes.





 I want to keep my current DNS provider for my domain (example.com). Can I delegate a subdomain (subdomain.example.com) from my current DNS provider to CIS? 

Yes. The process is similar to adding a domain, but instead of the registrar, you work with the DNS provider for the higher level domain. When you add a subdomain to CIS, you are given two name servers to configure, as usual. You configure a Name Server (NS) record for each of the two name servers as DNS records within your domain being managed by the other DNS provider. When we are able to verify that the required NS records have been added, we activate your subdomain. If you do not manage the higher level domain within your organization, you must work with the owner of the higher level domain to get the NS records added.
Export BIND config.

ibmcloud cis dns-records-export DNS_DOMAIN_ID [--file FILE] [-i, --instance INSTANCE]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

--file
: The BIND config file that saves exported DNS records.

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





 Examples 

Export BIND config for domain 31984fea73a15b45779fa0df4ef62f9b.

ibmcloud cis dns-records-export 31984fea73a15b45779fa0df4ef62f9b --file bind_config_file.txt -i "cis-demo"









 Domain 

Manipulate domains by using the following domain commands.



 ibmcloud cis domain-add 

Add a domain.

ibmcloud cis domain-add DNS_DOMAIN_NAME [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

type value
: Specify the domain type setup. Valid values: full, partial (default full).



* full: A full zone implies that DNS is hosted.
* partial: A partial zone implies that CNAME setup domain.



jump-start
: Automatically attempt to fetch existing DNS records.

DNS_DOMAIN_NAME
: The FQDN 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.





 Examples 

Add a new domain test.com in instance cis-demo.

ibmcloud cis domain-add "test.com" -i "cis-demo"







 ibmcloud cis domain-resume 

Resume the given domain.
* Wildcard records are only allowed for the following record types.



* A
* AAAA
* CNAME
* MX



* PTR records are not supported for A and AAAA type wildcard records.
* [Importing DNS records](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-managing-dns-zonesimport-resource-records-api) does not support wildcard records.
* To avoid causing conflicts when importing a DNS zone file, do not create or delete DNS records until the import is complete.
* When importing a DNS zone file, ensure that no other import operations occur that might cause a conflict.







 Managing wildcard DNS records 

You can manage a wildcard record the same way as any other record. Refer to [Managing DNS records](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-managing-dns-records) to learn more about creating, reading, updating, and deleting wildcard records.
[Deprecated] ibmcloud cis dns-record-update DNS_DOMAIN_ID DNS_RECORD_ID --json-file JSON_FILE [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

DNS_RECORD_ID
: The ID of DNS record. Required.

--name
: DNS record name.

--type
: DNS record type.

--content
: DNS record content.

--ttl
: Time to live for DNS record. Value of 1 is automatic. The default value is 1.

--proxied
: Control whether or not traffic should flow through the security and performance functions on CIS. CIS only proxies traffic for A, AAAA, and CNAME records. Valid values: true, false.

--json
: The JSON file or JSON string used to describe a DNS Record. Supported DNS Record types are: A, AAAA, CNAME, NS, TXT, MX, LOC, SRV, CAA,PTR.



* For type A, AAAA, CNAME, NS, TXT:



* The required fields in JSON data are name, type, content.
* The optional fields are ttl, proxied:



* proxied Control whether or not traffic should flow through the security and performance functions on CIS. CIS only proxies traffic for A, AAAA, and CNAME records.







Sample JSON data:

{
"name": "testA",
"type": "A",
"content": "127.0.0.1",
"proxied": true
}

{
"name": "testAAAA",
"type": "AAAA",
"content": "2001:0db8:0012:0001:3c5e:7354:0000:5db1",
"proxied": false
}
If you are unsure of who the registrar is for your domain, you can look it up at [whois.icann.org](https://whois.icann.org/).

If you delegate a subdomain (for instance, subdomain.example.com) from another DNS provider, you must replace the existing name server (NS) records and replace them with a name server record for each of the name servers that are provided by CIS. See [Managing DNS records in Cloudflare](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/) for detailed instructions by provider.

After you configure your registrar or DNS provider, it can take up to 24 hours for the changes to take effect. When we verify that the specified name servers were configured correctly for your domain or subdomain, the domain's status changes from Pending to Active.

Your domain must move to Active state within 60 days or your domain and any configuration data is removed.





 Step 5. Ensure that CIS is resolving the domain information for your application, hostname, or website 

To proceed, select Reliability > DNS. Be sure to add the appropriate DNS records. Add the A Record and any AAAA or MX entries that are populated. If you forget to add these records before the registrar's delegation is complete, IBM Cloud Internet Services cannot resolve the domain information for your internet-facing applications.







 Next steps 

To begin managing CIS functions and features, see [Managing your IBM Cloud Internet Services deployment](https://cloud.ibm.com/docs/cis?topic=cis-manage-your-cis-deployment).
dns_records_import](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_dns_records_import)<br> * [ibm_cis_domain](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_domain)<br> * [ibm_cis_domain_settings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_domain_settings)<br> * [ibm_cis_edge_functions_action](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_edge_functions_action)<br> * [ibm_cis_edge_functions_trigger](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_edge_functions_trigger)<br> * [ibm_cis_filter](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_filter)<br> * [ibm_cis_firewall](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_firewall)<br> * [ibm_cis_firewall_rules](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis_firewall_rules
ibmcloud cis custom-pages [-d, --domain DNS_DOMAIN_ID] [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

`-d, --domain
: DNS Domain ID.

-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.





 Examples 

List existing custom pages for domain 31984fea73a15b45779fa0df4ef62f9b.

ibmcloud cis custom-pages -d 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"









 DNS record 

Manipulate how the DNS Record performs using the following dns-record commands:



 ibmcloud cis dns-record-create 

Create a DNS record for a given domain of a service instance.

ibmcloud cis dns-record-create DNS_DOMAIN_ID (--json @JSON_FILE | JSON_STRING) [-i, --instance INSTANCE] [--output FORMAT]
ibmcloud cis dns-record-create DNS_DOMAIN_ID --type TYPE --name NAME --content CONTENT [--ttl TTL] [-i, --instance INSTANCE] [--output FORMAT]
[Deprecated] ibmcloud cis dns-record-create DNS_DOMAIN_ID --json-str JSON_STR [-i, --instance INSTANCE] [--output FORMAT]
[Deprecated] ibmcloud cis dns-record-create DNS_DOMAIN_ID --json-file JSON_FILE [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

--name
: DNS record name.

--type
: DNS record type.

--content
: DNS record content.
From here, you can make changes to the DNS zone, and click Update SOA to commit the changes.

The DNS Edit Zone page allows you to add new records and edit existing records for the zone. You can also export or delete the zone from this page.





 Delete a DNS zone 

After a DNS zone is added, it can be deleted at any time. DNS zone deletions are permanent; they cannot be undone. Follow these steps to delete a DNS zone in the DNS Forward Zones page:



1. Select the Delete icon at the end of the row containing the DNS zone. A confirmation dialog appears.
2. Click the Yes button to confirm the deletion, or click the No button to cancel the action.



Zones can also be deleted from within the Edit DNS Zones page.
Setting up your Domain Name System for CIS 

Read some specific instructions about how to configure your IBM Cloud® Internet Services Domain Name System (DNS) records, including how to configure Secure DNS.



 Adding DNS records 

You can use the Type list menu to select the type of record you want to create. Each DNS record type has a Name and Time-To-Live (TTL) associated with it.

Whatever is entered into the Name field has the domain name appended to it unless the domain name is manually appended in the field already (for example, if www or www.example.com is typed into the field, the API handles both as www.example.com). If the exact domain name is typed into the name field, then it won't be appended on itself (for example, example.com is handled as example.com). However, the list of DNS records only shows the names without the domain name added, so www.example.com is shown as www and example.com is shown as example.com. The TTL has a default value of Automatic, but can be changed by the user. A proxied DNS record always has a TTL of Automatic, so a newly proxied record adopts this configuration during this change.

For records such as A record, CNAME, and so on, the automatic TTL is 300s.



 A Type record 

To add this record type, valid values must exist in the Name and IPv4 Address fields. A TTL also can be specified from the list menu, with a default value of Automatic.

Required Fields: Name, IPv4 Address Optional Field: TTL (default value is Automatic)





 AAAA Type record 

To add this record type, valid values must exist in the Name and IPv6 Address fields. A TTL also can be specified from the list menu, with the default value of Automatic.

Required Fields: Name, IPv6 Address Optional Field: TTL (default value is Automatic)





 CNAME Type record 

To add this record type, a valid value must exist in the Name field and a fully qualified domain name must be in the Domain Name (FQDN) field.
"ttl": 60,
"name": "www.example.com",
"id": "A:ec0c4ee2-5d1f-4066-bcf2-dc9f3122c639",
"rdata": {
"ip": "192.168.10.100"
}
}
]
}







 Updating a resource record 



 Request 

curl -X PUT $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID/resource_records/$RECORD_ID -H "Authorization: $TOKEN" -d '{
"name":"www",
"rdata": {
"ip":"7.7.7.7"
},
"ttl":300
}'





 Response 

{
"created_on":"2019-09-10 20:03:25.249355942 +0000 UTC",
"modified_on":"2019-09-11 16:13:17.350043736 +0000 UTC",
"rtype":"A",
"ttl":300,
"name":"www",
"id":"A:139eb9f3-c646-4eb6-92fa-3ddabfb1b84f",
"rdata":{
"ip":"7.7.7.7"
}
}







 Deleting a resource record 



 Request 

curl -X DELETE $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID/resource_records/$RECORD_ID -H "Authorization: $TOKEN"





 Response 

HTTP 204 is returned, no content in response.







 Importing bulk resource records from a DNS zone file 



 Request
$ whois 104.28.22.57 | grep OrgName
OrgName: IBM

If you would rather bypass CIS on a domain (we still resolve DNS), then non-proxying the record is a possible solution.





 I got a DNS Validation error: 1004; now what can I do? 

For page rules to work, DNS needs to resolve for your zone. As a result, you must have a proxied DNS record for your zone.





 Can I add a CNAME for a root record? 

Yes. IBM CIS supports a feature called "CNAME Flattening" which allows our users to add a CNAME as a root record. Our authoritative DNS servers enumerate the CNAME target's records and respond with those records instead of the CNAME itself, effectively hiding the fact that the user configured a CNAME at the root of the domain.





 What is the default health check timeout? 

The default health check timeout for the Free Trial and Standard plans is 60 seconds.





 Can health checks be configured for non-HTTP/HTTPS traffic? 

No, health checks can only be configured with HTTP/HTTPS.





 Can global load balancers be configured for non-HTTP/HTTPS traffic? 

No, global load balancers can only be configured with HTTP/HTTPS.





 Does disabling all of my origins in an origin pool disable the entire pool itself? 

Yes, if the origin pool is being used in a load balancer, the traffic is routed to the next highest priority pool or the fallback pool.





 I have an error in my Kubernetes Ingress, what do I do? 

The hostname in a Kubernetes ingress must consist of lower case alphanumeric characters, - or ., and must start and end with an alphanumeric character. Using _ in the load balancer name, though permitted, can cause an ingress error in Kubernetes clusters. We recommend that you not use - in the load balancer name to avoid issues with Kubernetes clusters.





 I got a 502 error attempting to save an Edge Functions Action, what do I do?