vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* For example, if your CIS domain is foo.com, you have a COS bucket called images and your public COS endpoint is s3.us-west.objectstorage.uat.test.net then CIS creates a CNAME as images.foo.com that points to images.s3.us-west.objectstorage.uat.test.net.



If the Resolve Override with COS page rule is no longer needed the CNAME should be manually deleted along with the page rule.
* Host Header Override



* The Host Header Override setting replaces the host header for the URI matching the page rule to <bucket-name>.<cos-endpoint>.
* Using the previous example, the Host Header Override value is set to images.s3.us-west.objectstorage.uat.test.net.
* [Deleting Schematics objects from UI](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-ui)



* [Workspaces](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-wkscategory)
* [Actions](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-actionscategory)
* [Inventories](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-invcategory)



* [Deleting Schematics objects from CLI](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-cli)



* [Workspaces](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-cliwks)
* [Actions](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-cliactions)
* [Inventories](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-cliinvcategory)
classic_infrastructure_username = "password"
}







 Deleting a DNS provider configuration in the UI 

If you no longer need a configuration, you can delete it by using the Secrets Manager UI.

After you delete a configuration, the certificates that are associated with the DNS provider can no longer be rotated automatically. Do not delete configurations that are associated with certificates in your production apps or services.



1. In the console, click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/icon_hamburger.svg)> Resource List.
2. From the list of services, select your instance of Secrets Manager.
3. In the Secrets engines page, click the Public certificates tab.
4. Use the DNS providers section table to view the configurations in your instance.
5. In the row for the configuration that you want to delete, click the Actions menu ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/actions-icon-vertical.svg)> Delete.
6. Enter the name of the configuration to confirm its deletion.
7. Click Delete.







 Deleting a DNS provider configuration with the API 

You can delete configurations by calling the Secrets Manager API.

The following example shows a query that you can use to remove a DNS provider configuration from your instance. When you call the API, replace {config_name} with the name of the configuration that you want to delete.

After you delete a configuration, the certificates that are associated with the DNS provider can no longer be rotated automatically. Do not delete configurations that are associated with certificates in your production apps or services.

curl -X DELETE
Deletion of a subset of data is not supported.

For example, deletion of data that is collected from 1 monitoring agent in a Monitoring instance is not supported.





 Deleting captures 

When you delete a capture, the data file for that capture is automatically deleted.





 Deleting an IBM Cloud Monitoring instance 

When you delete an instance of IBM Cloud Monitoring from the IBM Cloud, you must open a case through support to request the data to be deleted. For more information, see [contacting support](https://cloud.ibm.com/docs/monitoring?topic=monitoring-gettinghelpgettinghelp).
[menu icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/icons/icon_hamburger.svg) > Observability to access the Observability Dashboard.
3. Click Logging. The list of logging instances is displayed.
4. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/icons/action-menu-icon.svg) next to the instance that you want to delete.
5. Click Delete.







 Removing an instance through the CLI 

To remove an instance of IBM Log Analysis through the command line, complete the following steps:



1. [Pre-requisite] Install the IBM Cloud CLI.

For more information, see [Installing the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).
2. Log in to IBM Cloud. Run the following command: [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login)
3. Get information about the instance that you plan to delete.

ibmcloud resource service-instance INSTANCE-NAME --output JSON
4. Remove any service key associated with the instance.

Find the service keys that are associated with an instance:

ibmcloud resource service-keys --instance-id INSTANCE-GUID

Run the following command to delete 1 service key. You must delete all.

ibmcloud resource service-key-delete SERVICE-KEY-NAME
5. Remove the instance.
oc get all -A | grep portworx
8. Remove the Portworx service instance from your IBM Cloud account.



1. From the [IBM Cloud resource list](https://cloud.ibm.com/resources), find the Portworx service that you created.
2. From the actions menu, click Delete.
3. Confirm the deletion of the service instance by clicking Delete.





To stop billing for Portworx, you must remove the Portworx Helm installation from your cluster and remove the Portworx service instance from your IBM Cloud account.
* UI
* CLI
* API







 Deleting a workspace 

After you destroy all associated VPC resources, if you don't need the workspace anymore, you can also delete the Schematics workspace.



 Deleting a workspace using the UI 



1. In the IBM Cloud console on the Schematics > Workspaces page, select Actions > Delete workspace to delete the schematics workspace.
2. Confirm the action by entering the workspace name in the text box and click Delete workspace.







 Deleting a workspace using the CLI 

Run the following command to delete your workspace:

ibmcloud schematics workspace delete --id <WORKSPACE_ID>

You can monitor the log files to view the deletion progress of your workspace.





 Deleting a workspace using the API 



1. To delete a workspace by using the IBM Cloud Schematics Python APIs, create a Python file and provide a name of your choice, for example, schematics_delete_workspace.py.
2. Copy and paste the [Delete a workspace using Schematics Python API](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-deleting-workspaceexample-request-delete-workspace) example request to your Python file.
3. Change the following parameters as part of the request:



* Replace your IBM Cloud key to the authenticator = IAMAuthenticator('<ibm-api-key>') variable.
* Change the API endpoint to the endpoint mentioned in [API endpoints](https://cloud.ibm.com/apidocs/schematics?code=pythonapi-endpoints) according to the location that you want your Schematics workspace to reside, for example, schematics_service.set_service_url('https://us.schematics.cloud.ibm.com').



4. Inside the schematics_service.delete_workspace function, provide the following parameters:
(Optional) If you would like to delete/destroy the VPC resources which was created, go back to the Schematics Workspace and select Actions > Destroy resources. ![DestroyResources](https://cloud.ibm.com/docs-content/v1/content/d50364af907081c3c38f99c11f35dd9cab4b2510/vpc-journey/images/provision-vpc/destroy-resources.png)









 Additional VPC Deployment Patterns and Resources 

Now that you understand how to deploy a VPC, explore some additional deployment patterns using the resources below:



* [Multi-Zone VPC](https://github.com/Cloud-Schematics/gcat-multizone-vpc)
* [IBM Cloud Tutorials - Public Frontend and Private Backend Subnets](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-public-app-private-backend)
* [Hub-n-Spoke VPC](https://cloud.ibm.com/docs/vpc-journey?topic=vpc-journey-vpc-advanced-elements)







 Next Steps 

The next step on the deployment journey is:



* [Establish Transit Gateway Connectivity](https://cloud.ibm.com/docs/vpc-journey?topic=vpc-journey-vpc-tgw)
You can delete them anytime by using the Snapshots for VPC list.

Use the following steps to delete a remote region copy by using the UI.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Snapshots.
2. Click the Actions menu (ellipsis) in the row of the snapshot that you want to delete.
3. Select Delete.
4. Confirm the deletion and click Delete.







 Creating a remote region copy from the CLI 

New

You can create a cross-regional copy of a snapshot by using the snapshot-create command with the --source-snapshot-crn option and the source snapshot CRN, which creates a snapshot in the target region by using the CRN of a snapshot from the source region. The created snapshot uses the customer-defined encryption key if the CRN of an encryption key was also specified.

ibmcloud is snapshot-create --name my-cli-snapshot-crc --source-snapshot-crn crn:v1:staging:public:is:us-south:a/2d1bace7b46e4815a81e52c6ffeba5cf::snapshot:r134-b9590a48-63a3-445e-b819-3f2c0b82daf8

Creating snapshot my-cli-snapshot-crc under account Test Account as user test.user@ibm.com...

ID r142-bd4532c0-e73c-44f9-a017-89e5368c521a
Name my-cli-snapshot-crc
*  UI







  Deleting bandwidth pools 

To delete a bandwidth pool by using the UI, follow these steps:



1.  From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2.  Select the Navigation menu ![Navigation menu](https://cloud.ibm.com/docs-content/v1/content/62b0b227c55ca35d2081883daccc11ef3a59022a/icons/icon_hamburger.svg), then click Classic Infrastructure.
3.  Select Network > Bandwidth > Pools.
4.  Locate the bandwidth pool that you want to cancel. Use the Region and Overage Status filters as necessary.
5.  Click the Actions menu ![Actions menu](https://cloud.ibm.com/docs-content/v1/content/62b0b227c55ca35d2081883daccc11ef3a59022a/icons/action-menu-icon.svg) for the bandwidth pool and select Delete.
6.  Acknowledge the scheduled cancellation date, and click Delete.

The pool remains active and continues to meter until it is permanently deleted at the end of your billing cycle.
7.  Select Scheduled in the Deletion column to check the scheduled cancellation date of the bandwidth pool or to unschedule the bandwidth pool deletion. For more information, see [Unscheduling deletion of bandwidth pools](https://cloud.ibm.com/docs/bandwidth-pools?topic=bandwidth-pools-how-to-unscedule-deletion-ibm-cloud-bandwidth-pools).



Alternatively, you can access the bandwidth pool's details page to delete a bandwidth pool. In the upper right of the bandwidth pool's details page, click the Actions menu ![Actions menu](https://cloud.ibm.com/docs-content/v1/content/62b0b227c55ca35d2081883daccc11ef3a59022a/icons/action-menu-icon.svg), then click Delete.
*  UI
*  CLI
*  API







  Deleting a linked zone 

Delete a linked zone by using the UI, CLI, or API.



  Deleting a linked zone using the UI 

To delete a linked zone using the UI, take the following steps:



1.  Navigate to the Zones section of your DNS Services instance, then select the Linked zones tab.
2.  Click overflow menu ![Overflow menu icon](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/dns-svcs/images/overflow-icon.png) of the linked zone you want to delete.
3.  Select Delete linked zone.







  Deleting a linked zone using the CLI 

To delete a linked zone using the CLI, run the following command:

ibmcloud dns cross-account linked-zone-delete LINKED_ZONE_ID [-i, --instance INSTANCE] [--output FORMAT]

Where:



*  LINKED_ZONE_ID is the ID of linked zone.
*  -i, --instance value is the instance name or ID. If not set, the context instance specified by ibmcloud dns instance-target INSTANCE is used.
*  --output value specifies the output format. Currently, json is the only supported format.







  Deleting a linked zone using the API 

To delete a linked zone using the API, follow these steps:



1.  Set up your API environment with the correct variables.
2.  Store the following values in variables to be used in the API command:



*  INSTANCE_ID, which is the unique identifier of a service instance.
*  LINKED_DNSZONE_ID which is the unique identifier of a linked zone.
*  IAM_TOKEN, which is the IAM authorization token.



3.  When all variables are initiated, delete the linked zone:

curl -X DELETE     https://api.dns-svcs.cloud.ibm.com/v1/instances/$INSTANCE_ID/linked_dnszones/$LINKED_DNSZONE_ID     -H "Authorization: $IAM_TOKEN"
Resize Vertically scale virtual server instances to any supported profile size. For more information, see [Resizing a virtual server instance](https://cloud.ibm.com/docs/vpc?topic=vpc-resizing-an-instance). 
 Delete To delete an instance, the instance must have a powered off status. If the instance has a floating IP address, it must be unassociated or released before the instance is deleted. The delete action permanently removes an instance and its connected vNIC, boot volume, and data from your account. If auto-delete is enabled, the associated boot volume is also deleted. 
 Host failure auto restart Toggle on or off the host failure restart policy for an instance. For more information, see [Host failure recovery policies](https://cloud.ibm.com/docs/vpc?topic=vpc-host-failure-recovery-policies&interface=api). 







 Rename a virtual server instance using the UI 

From the Virtual server instances page in IBM Cloud console, click Rename. Enter the new name for the virtual server instance. Click Rename.





 Rename a virtual server instance using the CLI 

You can rename a virtual server instance in your IBM Cloud VPC by using the command-line interface (CLI).

To rename a virtual server instance by using the CLI, use the ibmcloud is instance-update INSTANCE command. Specify the new name of the instance with the --name NEW_NAME option.

The following example renames a virtual server with the name of my-instance-name to my-instance-name-new.

ibmcloud is instance-update my-instance-name --name my-instance-name-new

For a full list of command options, see [ibmcloud is instance-update](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceinstance-update).





 Rename a virtual server instance using the API 

You can rename the virtual server instance in your IBM Cloud VPC by using the API.

The following example renames a virtual server instance from name to my-instance.
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-origin-certificate-create" "> --><-- <section "id="section-command-example-origin-certificate-create" "> --> Examples Create a CIS-signed certificate for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis origin-certificate-create 31984fea73a15b45779fa0df4ef62f9b --request-type origin-rsa --hostnames ".example.com" --hostnames "example.com" --requested-validity 5475 --csr your_csr -i cis-demo --output JSON

ibmcloud cis origin-certificate-create 31984fea73a15b45779fa0df4ef62f9b --json '{"hostnames":"example.com",".example.com"] ! ! !
app sat-aws-block-bronze
2. Remove the pod that uses the PVC. If the pod is part of a deployment, remove the deployment.

oc delete pod <pod_name>

oc delete deployment <deployment_name>
3. Verify that the pod or the deployment is removed.

oc get pods

oc get deployments



3. Delete the PVC. Because all IBM-provided AWS EBS storage classes are specified with a Delete reclaim policy, the PV and the AWS EBS instance in your AWS account are automatically deleted when you delete the PVC.

oc delete pvc <pvc_name>
4. Verify that your storage is removed.



1. Verify that your PV is automatically removed.

oc get pv
2. From the [AWS EC2 dashboard](https://console.aws.amazon.com/ec2/v2/home), select Elastic Block Store > Volumes and verify that your AWS EBS instance is removed.









 Removing the AWS EBS storage configuration from your cluster 

If you no longer plan on using AWS EBS storage in your cluster, you can unassign your cluster from the storage configuration.

Note that if you remove the storage configuration, the driver is then uninstalled from all assigned clusters. Your PVCs, PVs and data are not removed. However, you might not be able to access your data until you re-install the driver in your cluster again.



 Removing the AWS EBS storage configuration from the console 

Use the console to remove the AWS EBS storage configuration.

Note that you must delete your storage assignments before you can successfully delete your storage configuration.



1. From the Satellite storage dashboard, select the storage configuration you want to delete.
2. Select Actions > Delete
3. Enter the name of your storage configuration.
4. Select Delete.







 Removing the AWS EBS storage configuration from the CLI 

Use the CLI to remove the AWS EBS storage configuration.
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/actions-icon-vertical.svg)> Delete.
6. Enter the name of the configuration to confirm its deletion.
7. Click Delete.







 Deleting a certificate authority configuration with the API 

You can delete configurations by calling the Secrets Manager API.

The following example shows a query that you can use to remove a certificate authority configuration from your instance. When you call the API, replace {config_name} with the name of the configuration that you want to delete.

After you delete a configuration, the certificates that are associated with the certificate authority can no longer be rotated automatically. Do not delete configurations that are associated with certificates in your production apps or services.

curl -X DELETE
--H "Authorization: Bearer {iam_token}" "https://{instance_ID}.{region}.secrets-manager.appdomain.cloud/api/v2/configurations/{name}"

A successful response removes the configuration from your service instance. For more information about the required and optional request parameters, see [Remove a configuration](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2delete-config-element).





 Next steps 



* [Add a DNS provider configuration](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-add-dns-provider)
* [Order a certificate](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-public-certificatesorder-public-certificates)
[Actions](https://cloud.ibm.com/docs-content/v1/content/ad5f41087138b4b1bb795e3b5b0661ac5a105cbd/icons/action-menu-icon.svg) > Delete to delete the mapping.







 Deleting domain mappings with the CLI 

To delete a custom domain mapping with the CLI, use the [ibmcloud ce domainmapping delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-domainmapping-delete) command.

You can delete only custom domain mappings, and not domain mappings that are generated by Code Engine. Run the [ibmcloud ce domainmapping list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-domainmapping-get) command to display a list of custom domain mappings with the CLI. A custom domain mapping has a generated CNAME record. In the CLI, you can obtain the generated CNAME value for a specified custom domain mapping by using the [ibmcloud ce domainmapping get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-domainmapping-get) command.

ibmcloud ce domainmapping delete --domain-name www.example.com -f

Example output

Deleting domain mapping 'www.example.com'...
OK
* To remove images individually from your namespace, use the [ibmcloud cr image-rm](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_rm) command. Replace <image_name> with the name of the image that you want to remove. The name must be in the format repository@digest or repository:tag. If a tag is not specified in the image name, the image that is tagged latest is deleted by default. Deleted images are stored in the trash for 30 days. Images that are in the trash don't count toward your quota.

You can remove both tagged and untagged images by using the format repository@digest. You can remove only tagged images by using the format repository:tag.

ibmcloud cr image-rm <image_name>

Where multiple tags exist for the same image digest within a repository, the [ibmcloud cr image-rm](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_rm) command removes the underlying image and all its tags. If the same image exists in a different repository or namespace, that copy of the image is not removed. If you want to remove a tag from an image and leave the underlying image and any other tags in place, see [Removing tags from images in your private repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_untag) command.
* To remove untagged images collectively from your namespace, use the [ibmcloud cr image-prune-untagged](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcliic_cr_image_prune_untagged) command, see [Clean up your namespaces by deleting untagged images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionretention_images_untagged).
Command options 

NAMESPACE
: The namespace that you want to remove.

--force, -f
: (Optional) Force the command to run with no user prompts.





 Example 

Remove the namespace birds.

ibmcloud cr namespace-rm birds







 ibmcloud cr plan 

Displays your pricing plan for the registry region that you're targeting.

ibmcloud cr plan



 Prerequisites 

To find out about the required permissions, see [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).







 ibmcloud cr plan-upgrade 

Upgrades you to the standard plan for the registry region that you're targeting.

ibmcloud cr plan-upgrade [PLAN]

For more information about plans, see [Registry plans](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_plans).



 Prerequisites 

To find out about the required permissions, see [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).





 Command options 

PLAN
: (Optional) The name of the pricing plan that you want to upgrade to. If PLAN is not specified, the default is standard.





 Example 

Upgrade to the standard pricing plan.

ibmcloud cr plan-upgrade standard







 ibmcloud cr platform-metrics 

You can use the command to enable and disable platform metrics. You can also use it to find out whether you have platform metrics set up on your account for the registry region that you're targeting.

If you want to view the platform metrics for IBM Cloud Container Registry, you must opt in by running the ibmcloud cr platform-metrics command.

You must specify one of the command options or the command fails with an error.

ibmcloud cr platform-metrics --enable | --disable | --status