vania-janet/multiturn-rag-retrieval-data huggingface dataset:
(https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-timeout) for assistance.
3. Verify that the image was deleted by running the following command, and check that the image does not show in the list.

ibmcloud cr image-list







 Deleting images from your private repository in the console 

You can delete unwanted images and all their tags from your private IBM Cloud image repository by using the IBM Cloud console.

Deleting an image that is being used by an existing deployment might cause scale-up, reschedule, or both, to fail.

If you want to restore a deleted image, you can list the contents of the trash by running the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command and restore a selected image by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command.

To delete an image by using the IBM Cloud console, complete the following steps:



1. Log in to the IBM Cloud console [https://cloud.ibm.com/login](https://cloud.ibm.com/login) with your IBMid.
2. If you have multiple IBM Cloud accounts, from the account menu, select the account and region that you want to use.
3. Click the Navigation menu icon, then click Container Registry.
4. Click Images. A list of your images is displayed.
5. In the row that contains the image that you want to delete, select the checkbox.
6. Click Delete Image.









 Listing images in the trash 

You can list deleted images that are in the trash and see when they expire.

To find out which images are in the trash, you can use the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command.
[List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/6da1ae87b1f476791c38688e7a0b7f7c7a7d71b9/databases-for-elasticsearch/includes/cloud-databases/includes/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI 

By using the CLI, you can delete your existing IBM Cloud® Databases instance with the [ibmcloud resource service-instance-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_delete) command:

ibmcloud resource service-instance-delete my-service-instance

Using the command ibmcloud resource reclamation-delete deletes a reclaimed resource so that the resource can no longer be restored.





 Deleting your database by using DROP DATABASE Statement 

[DROP DATABASE](https://dev.mysql.com/doc/refman/5.7/en/drop-database.html) drops all tables in the database and deletes the database.

DROP {DATABASE | SCHEMA} [IF EXISTS] db_name





 Deleting your database by using mysqladmin 

You can also drop databases with [mysqladmin, a MySQL Server Administration Program](https://dev.mysql.com/doc/refman/5.7/en/mysqladmin.html). Launch mysqladmin like this:

mysqladmin [options] command [command-arg] [command command-arg]] ...





 Cryptoshredding keys 

Key Protect provides for a [force delete](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-keys) of a key that is in use by IBM Cloud® services, including your Cloud Databases deployments.
Any user who has been authorized to the catalog offering version can [provision a virtual server instance](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance) with that image by specifying the offering version's CRN as catalog_offering.version.crn. Alternatively, users can specify the offering's CRN as catalog_offering.offering.crn to provision a virtual server instance with the latest image associated with the catalog offering. For more information, see [Custom images in a private catalog](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images&interface=apiprivate-catalog-image-reference-vpc-api) in Getting started with custom images, the tutorial [Onboarding a virtual server image for VPC](https://cloud.ibm.com/docs/account?topic=account-catalog-vsivpc-tutorial), and the [Import offering](https://cloud.ibm.com/apidocs/resource-catalog/private-catalogimport-offering) method in the Catalog Management API.

The image may not be deleted or used in a different catalog product offering version while it is managed from a catalog. If the catalog is deleted, a 7 day reclamation period will apply that prevents any images managed by the catalog from being deleted or re-used during the reclamation period. For more information, see [Deleting a custom image in a private catalog](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images&interface=apideleting-private-catalog-custom-image-vpc) and [Using resource reclamations](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation&interface=apirestore-resource-cli).

Image references may refer to custom images in other accounts. Before using this feature, verify that your clients handle image reference lookup failures gracefully and do not assume inaccessible images have been deleted, even when running with full access to your images. To avoid possible retrieval or use of the wrong image by name, specify the image id, crn, or href instead.
Cancelling your billing items 

You're billed for resources in your account until you cancel them. If you deleted a resource or have resources in your account that are no longer used, make sure to cancel all billing items associated with those resources. Billing items can't be recovered after they are canceled.

To cancel billing items, complete the following steps:



1.  If you haven't deleted the resource, you need to do so:



1.  From your dashboard, click View resources in the Resources summary widget.
2.  Expand the sections to locate the service instance that you want to delete.
3.  Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/9713d864488177dc6b273b53b7f2383a81f10bc1/icons/action-menu-icon.svg) > Delete for the row.



2.  After you delete your resource, from the IBM Cloud console, go to Manage > Billing and usage and select Billing items.
3.  Expand the items to find any associated billing items to resources that you deleted.
4.  Click Actions > Cancel Billing Item.
5.  Select Immediately or Anniversary Date to specify when to cancel the item.
6.  Click Continue.
7.  Acknowledge that data loss might occur and click Cancel Service.
* UI
* CLI
* API
* Terraform







 Deleting a Continuous Delivery service instance 

You can delete resource group-based Continuous Delivery service instances.

To delete a Continuous Delivery service instance, you must have either the Administrator or Editor user permissions.

Deleting an instance of the Continuous Delivery service impacts your ability to use tool integrations within toolchains that are contained in the same region and resource group as the deleted service instance. For more information about this limitation, see [Plan limitations and usage](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-limitations_usage).



 Deleting a Continuous Delivery service instance by using the console 



1. Log in to [IBM Cloud](http://cloud.ibm.com).
2. Go to the [Resource list](https://cloud.ibm.com/resources) for your IBM Cloud account.
3. In the Services section, locate the active Continuous Delivery service instance.
4. From the Continuous Delivery service instance's Actions![Overflow icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/overflow-icon-2.svg) menu, click Delete.
5. Click Delete to confirm that you want to delete the Continuous Delivery service.







 Deleting a Continuous Delivery service instance from the CLI 



1. Log in to IBM Cloud by using the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).

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 you use this option, go to the link that is listed in the CLI output to generate a one-time passcode.
2.
[List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/c1b02d6157702384a9668d8c58bb951e69117793/databases-for-redis/includes/cloud-databases/includes/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI 

By using the CLI, you can delete your existing IBM Cloud® Databases instance with the [ibmcloud resource service-instance-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_delete) command:

ibmcloud resource service-instance-delete my-service-instance

Using the command ibmcloud resource reclamation-delete deletes a reclaimed resource so that the resource can no longer be restored.





 Deleting your database by using DROP DATABASE Statement 

[DROP DATABASE](https://dev.mysql.com/doc/refman/5.7/en/drop-database.html) drops all tables in the database and deletes the database.

DROP {DATABASE | SCHEMA} [IF EXISTS] db_name





 Deleting your database by using mysqladmin 

You can also drop databases with [mysqladmin, a MySQL Server Administration Program](https://dev.mysql.com/doc/refman/5.7/en/mysqladmin.html). Launch mysqladmin like this:

mysqladmin [options] command [command-arg] [command command-arg]] ...





 Cryptoshredding keys 

Key Protect provides for a [force delete](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-keys) of a key that is in use by IBM Cloud® services, including your Cloud Databases deployments.
ibmcloud resource reclamation-restore "d9fendfwlw" --comment "need to use for another 3 months" --output JSON







 ibmcloud resource reclamation-delete 

Delete a reclaimed resource so that the resource can no longer be restored:

ibmcloud resource reclamation-delete ID [--comment COMMENT] [--f, --force]



 Command options 

ID
: ID of the resource reclamation

--comment
: Comments about the action

-f, --force
: Force deletion without confirmation





 Examples 

Delete a resource reclamation with ID d9fendfwlw:

ibmcloud resource reclamation-delete "d9fendfwlw"

Delete a resource reclamation with ID d9fendfwlw and leave a comment of no longer needed without confirmation:

ibmcloud resource reclamation-delete "d9fendfwlw" --comment "no longer needed" -f
[Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/icon_hamburger.svg) > Dashboard, and click any of the links that are listed in the Classic infrastructure widget.







 What causes resource restorations to fail? 

A resource restoration can fail if you try to restore a resource in a deleted resource group or the resource restoration request isn't submitted in time. Most requests must be submitted within 7 days.





 How do I retrieve details on a resource that is scheduled for reclamation? 

After the instance is deleted from the console, you can view it in your account by using the CLI in the SCHEDULED state. The SCHEDULED state indicates that this instance is scheduled for reclamation. For more information, see [Working with resources and resource groups](https://cloud.ibm.com/docs/account?topic=cli-ibmcloud_commands_resourcecommand-options-37).





 Can you restore a resource that is in a deleted resource group? 

You can restore a resource from a deleted resource group. [Create a support case](https://cloud.ibm.com/unifiedsupport/cases/add) in the IBM Cloud Support Center and specify in the description of the case that you want to restore the resource that's in a deleted resource group.
* UI
* CLI
* API







 Removing a permitted network from a linked zone 

Remove a permitted network from your linked zone by using the UI, CLI, or API.



 Removing a permitted network using the UI 

To remove a permitted network 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 the link in the Zone name column of the linked zone you want to view the Linked zone details page.
3. In the Permitted networks tab, click the overflow menu ![Overflow menu icon](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/dns-svcs/images/overflow-icon.png) of the permitted network you want to delete, and select Delete.







 Removing a permitted network using the CLI 

To remove a permitted network from your linked zone using the CLI, run the following command:

ibmcloud dns cross-account linked-zone-permitted-network-remove LINKED_ZONE_ID PERMITTED_NETWORK_ID [-i, --instance INSTANCE] [--output FORMAT]

Where:



* LINKED_ZONE_ID is the ID of the linked zone.
* PERMITTED_NETWORK_ID is the ID of the permitted network.
* -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.







 Removing a permitted network using the API 

To remove a permitted network from your 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.
[50s elapsed]
ibm_resource_instance.terraform_demo: Creation complete after 52s [id=crn:v1:bluemix:public:event-notifications:us-south:a/4a74f2c31f554afc88156b73a1d577c6:24547d88-e455-548f-cb6e-ge921g6d3025::]
ibm_en_topic.topic1: Creating...
ibm_en_destination.destination1: Creating...
ibm_en_destination.destination1: Still creating... [10s elapsed]
ibm_en_topic.topic1: Still creating... [10s elapsed]
ibm_en_topic.topic1: Creation complete after 12s [id=24547d88-e455-548f-cb6e-ge921g6d3025/7960f1fe-7991-4993-ad0c-38f12c78b3c8]
ibm_en_destination.destination1: Creation complete after 13s [id=24547d88-e455-548f-cb6e-ge921g6d3025/878ce8e6-75f9-41e6-913f-6b42f6945588]
ibm_en_subscription.subscription1: Creating...
ibm_en_subscription.subscription1: Creation complete after 4s [id=24547d88-e455-548f-cb6e-ge921g6d3025/b2d88ff9-da10-412a-9f7a-19f509ea83fb]

Apply complete! Resources: 4 added, 0 changed, 0 destroyed..
Show more





 Step 7: Validating resources 

Validate resources within the IBM Cloud by selecting the resource list in [resources](https://cloud.ibm.com/resources).
If registering multiple domains, select the Add Another option to populate additional blank fields for more domain entries.

Select the Delete icon to delete an entire entry from the page.
9. Click the Check Availability button to check whether the domain names are available. If all domains are available, proceed to the next step. If one or more domains are not available, try again with another domain.
10. Click the Continue button to register the domain.





 Next steps 

After you register a domain, you can use the [DNS interface](https://cloud.ibm.com/docs/dns?topic=dns-how-to-use-the-dns-interface) to manage it. When the domain's registration approaches its expiration date, you can [renew the domain](https://cloud.ibm.com/docs/dns?topic=dns-renew-an-existing-domain).
Updating resource record 'A:f20cfe91-b936-4bad-a8d1-f7afa4ac32a6' in zone 'example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae' for service instance 'DNS Services-km' ...
OK

ID A:f20cfe91-b936-4bad-a8d1-f7afa4ac32a6
Name www.example.com
Type A
Created On 2020-04-10 09:12:07.858707275 +0000 UTC
Modified On 2020-04-10 09:40:55.204076727 +0000 UTC
TTL 900
Data
ip 10.10.1.1





 Deleting a resource record 

Use ibmcloud dns resource-record-delete command followed by the zone ID and resource record ID to delete a resource record.

$ ibmcloud dns resource-record-delete $DNS_ZONE_ID PTR:f20cfe91-b936-4bad-a8d1-f7afa4ac32a6
Really delete resource record 'PTR:f20cfe91-b936-4bad-a8d1-f7afa4ac32a6' in zone 'example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae' for service instance 'DNS Services-km'? [y/N]> y
Deleting resource record 'PTR:f20cfe91-b936-4bad-a8d1-f7afa4ac32a6' in zone 'example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae' for service instance 'DNS Services-km' ...
OK
Because the monitoring data is stored in IBM Cloud Monitoring, you must be authenticated to an IBM Cloud Monitoring instance in your account. For more information, see [IBM Cloud monitoring services](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-monitoring).





 (Optional): Delete the resources 

You can delete resources, however, a resource can't be deleted if it's required by other resources. For example, a VPC can't be deleted if it contains instances, subnets, or public gateways. For instructions on deleting a VPC and all its resources, see [Deleting a VPC using the REST APIs](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting-using-api).





 Congratulations! 

You've successfully created and configured your VPC by using the REST APIs. To try out more API commands, see the [Virtual Private Cloud API](https://cloud.ibm.com/apidocs/vpc).
: The namespace that you want to clean up.

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

--json
: (Optional) Outputs JSON that contains the results of cleaning your namespace. This option must be used with --force.

--retain-untagged
: (Optional) Retain all untagged images when the retention policy is being processed. Only tagged images are analyzed and, if the images don't meet the criteria, they are deleted. If the option isn't specified, all tagged and untagged images are analyzed and, if the images don't meet the criteria, they are deleted.

--images
: Determines how many images to keep within each repository in the specified namespace. The newest images are retained. The age of images is determined by their build date. IMAGECOUNT is the number of images that you want to retain in each repository for the namespace.





 Example 

Retain the newest 20 images within each repository, in the namespace birds.

ibmcloud cr retention-run --images 20 birds

For more information about how to use the ibmcloud cr retention-run command, see [Retaining images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention).







 ibmcloud cr trash-list 

Displays all images in the trash in your IBM Cloud account. You can also see the number of remaining days until the image is removed from the trash. The number of remaining days until removal is rounded up. For example, if the time until removal is 2 hours, it shows as 1 day. Images remain in the trash for 30 days after they are deleted from your live repository.

If you want to restore an image from the trash, run the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command, see [Restoring images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_restore).
const params = {
id: {instance_id},
recursive: false,
};
await resourceControllerService.deleteResourceInstance(params);
})();

from ibm_platform_services import ResourceControllerV2
...
resource_controller_service = ResourceControllerV2.new_instance()
response = resource_controller_service.delete_resource_instance(
id={instance_id},
recursive=False
)

import {
"github.com/IBM/platform-services-go-sdk/resourcecontrollerv2"
}
...
resourceControllerServiceOptions := &resourcecontrollerv2.ResourceControllerV2Options{}
resourceControllerService, err := resourcecontrollerv2.NewResourceControllerV2UsingExternalConfig(resourceControllerServiceOptions)
deleteCdInstanceOptions := resourceControllerService.NewDeleteResourceInstanceOptions(
{instance_id},
)
deleteCdInstanceOptions.SetRecursive(false)
response, err := resourceControllerService.DeleteResourceInstance(deleteCdInstanceOptions)



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



Table 2. Variables for deleting the Continuous Delivery service with the API

 Variable Description 

 {iam_api_key} Your IAM API key. 
 {instance_id} The ID of the Continuous Delivery service instance that you want to delete. 
 {token} A valid IAM bearer token. 



For more information about deleting service instances, see [Deleting resource instances by using the API](https://cloud.ibm.com/docs/account?topic=account-delete-resource&interface=apidelete-resource-instance-api).
If you are using Mozilla® Firefox® as your browser, the license start and end dates might be displayed with no values on the Caveonix RiskForesight console. To resolve the issue, view the license information in another browser, such as Google Chrome™.

If you are experiencing this problem and the only browser you can use is Firefox, contact [Caveonix Support](https://www.caveonix.com/support/) for assistance.





 Procedure to delete Caveonix RiskForesight licenses 

Deleting Caveonix RiskForesight automatically deletes the initial Caveonix RiskForesight license that is originally associated with the service. However, you need to manually delete any other unwanted licenses from the Caveonix RiskForesight licenses table on the Resources page in the VMware Solutions console.

To delete the Caveonix RiskForesight service, you must do so in the IBM Cloud® for VMware Solutions console. For more information, see [Deleting services from vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingservices).



1. From the IBM Cloud for VMware Solutions console, click Licenses from the left navigation pane.
2. In the Caveonix RiskForesight licenses table, find the license to delete.
3. In the Actions column, click the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg).
4. In the Delete License window, click OK. The status of the license is changed to Removing. When the license deletion is completed, the license is no longer available in the Caveonix RiskForesight licenses table.







 Related links
Delete a service instance by running the [ibmcloud resource service-instance-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_delete) command, where NAME is the name of the service instance, exclusive with ID, and ID is the ID of the service instance, exclusive with NAME.

ibmcloud resource service-instance-delete (NAME|ID) [-f, --force] [--recursive]

For example, the following command deletes a resource service-instance that's named my-service-instance:

ibmcloud resource service-instance-delete my-service-instance







 Deleting resource instances by using the API 

You can programmatically delete a resource instance by calling the Resource Controller API as shown in the following sample request. For detailed information about the API, see [Resource Controller API](https://cloud.ibm.com/apidocs/resource-controller/resource-controllerdelete-resource-instance).



* Curl
* Java
* Python
* Go
* Node



curl -X DELETE https://resource-controller.cloud.ibm.com/v2/resource_instances/8d7af921-b136-4078-9666-081bd8470d94 -H 'Authorization: Bearer <>'

DeleteResourceInstanceOptions deleteResourceInstanceOptions = new DeleteResourceInstanceOptions.Builder()
.id(instanceGuid)
.recursive(false)
.build();

Response<Void> response = service.deleteResourceInstance(deleteResourceInstanceOptions).execute();

System.out.printf("deleteResourceInstance() response status code: %dn", response.getStatusCode());

response = resource_controller_service.delete_resource_instance(
id=instance_guid,
recursive=False
)