vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The following examples show how to delete resources from your IBM Cloud® Virtual Private Cloud, for every VPC resource, in the suggested order.

The following key facts are important to remember about deletion:



* A VPC cannot be deleted until it is empty.
* All containing resources must be deleted successfully before the parent resource can be deleted.
* If the resource is pending a deletion, it shows a deleting status when viewed in list queries.
* Most delete requests are asynchronous, which means that the resource might show a deleting status in list queries when it was not yet deleted completely.
* You must poll to make sure that the child resource is no longer in the list view before you try to delete the parent resource.



If the status of the resource changes from deleting to failed, you can try to delete the resource again. If you cannot delete a resource in failed status, [Contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).



 Step 1: Find all subnets within the VPC that you want to delete 

Before a VPC can be deleted, each of its subnets must be deleted. Get the ID of the VPC that you want to delete by running the following command and looking at the ID value:

ibmcloud is vpcs

Save the ID of the VPC in a variable so it can be used later, for example:

vpc="0738-3524fef5-da35-4622-bf9a-31614964649d"

To get the list of all subnets in your account, run the following command:

ibmcloud is subnets

Look at the VPC value to determine the subnets that need to be deleted. Save the ID of the subnet in a variable so it can be used later, for example:

subnet="0738-d31ce469-9b0f-44e1-87ce-0fc77d8b0e53"
preventKeyDeletion A boolean that filters registrations based on if a registered resource has a retention policy. <br> <br>For example, if you have multiple registrations in your instance, and you want to list only registrations where preventKeyDeletion is true, use ../registrations?preventKeyDeletion=true. <br> <br>You can also pair preventKeyDeletion with offest, limit, and urlEncodedResourceCRNQuery to search through your available resources. 
 urlEncodedResourceCRNQuery The resource CRN that you want to filter registrations by. <br> <br>For example, if you have multiple registrations in your instance, and you want to only view registrations that are associated with a specific Cloud Resource Name (CRN), use ../registrations?urlEncodedResourceCRNQuery="url_encoded_CRN". <br> <br>For more information, see [CRN query examples](https://cloud.ibm.com/docs/key-protect?topic=key-protect-view-protected-resourcescrn-query-examples). <br> <br>You can also pair urlEncodedResourceCRNQuery with offest, limit, and preventKeyDeletion to search through your available resources. 



You can also filter for a subset of registrations by specifying the limit and offset parameters at query time.

You can use the following example request to retrieve a filtered set of registrations.

$ curl -X GET "https://<region>.kms.cloud.ibm.com/api/v2/keys/<keyID_or_alias>/registrations?offset=<offset>&limit=<limit>" -H "accept: application/vnd.ibm.collection+json" -H "authorization: Bearer <IAM_token>" -H "bluemix-instance: <instance_ID>"

Replace the limit and offset variables in your request according to the following table.



Table 5. Describes the limit and offset variables.

 Variable Description 

 offset The number of registrations to skip.
The allowed values are k8-cluster, resource-instance, resource-alias, resource-binding, resource-group, vmware-solutions, cloud-objects-storage-infrastructure, block-storage, file-storage, cloud-backup.

creation_date
: The date on which the resource is created.

modification_date
: The last modification date of the resource. It is in the format yyyy-mm-ddThh:mm:ssZ

_objectType
: The type of the classic infrastructure resource. Allowed values are SoftLayer_Virtual_DedicatedHost, SoftLayer_Hardware, SoftLayer_Network_Application_Delivery_Controller, SoftLayer_Network_Subnet_IpAddress, SoftLayer_Network_Vlan, SoftLayer_Network_Vlan_Firewall and SoftLayer_Virtual_Guest.

tags, tagReferences.tag.name
: The tag attached to a resource. Use tagReferences.tag.name when searching for tags attached to classic infrastructure resources





 Examples 

Search for Resource Controller resources in the specified location (i.e. in us-south region):

ibmcloud resource search "region:us-south AND family:resource_controller"

Search for resources or aliases in the resource group with the specified ID:

ibmcloud resource search "(type:resource-instance OR type:resource-alias) AND (doc.resource_group_id:c900d9671b235c00461c5e311a8aeced)"

Search for resource groups with name default:

ibmcloud resource search "name:default AND type:resource-group"

Search for resource bindings for the specified service name:

ibmcloud resource search "service_name:cloud-object-storage AND type:resource-binding"

Search for a resource with the specified Cloud Resource Name (CRN):
Log in to the Active Directory appliance and open the DNS tools.
2. Go to the instance subdomain, which is the subdomain under the root domain. Its name resembles the name of the vCenter Server instance.
3. Remove the hostname entries for the specific deleted service appliances.
4. Open the associated reverse lookup table and remove the DNS entries from the table.







 Related links 



* [FAQ](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions)
If you no longer need an instance of App ID, you can delete the service instance and any data that is stored. You can also choose to delete your service instance by using the console.



1. Delete the service and place it in a reclamation period of 7 days.

ibmcloud resource service-instance-delete <serviceName>
2. Optional: To permanently delete your instance, get the reclamation ID.

ibmcloud resource reclamations --resource-instance-id <tenantID>

If you choose not to permanently delete the instance, the instance and data are still deleted at the end of the 7 day reclamation period.
3. Optional: Permanently delete the reclamation instance.

ibmcloud resource reclamation-delete <reclamationId>

If you permanently delete the instance, you cannot restore your data.







 Restoring a deleted instance 

If you didn't permanently delete your instance, you can restore it during the reclamation period.



1. Get the reclamation ID.

ibmcloud resource reclamations --resource-instance-id <tenantID>
2. Restore the reclamation.

ibmcloud resource reclamation-restore <reclamationID>
The default value is ["name"]. The list items must match the regular expression /^-?[a-z0-9_.\[\],-]+$/.

--all-pages (bool)
: Optional. Invoke multiple requests to display all pages of the collection for the associated resources.
* Example

ibmcloud hpcs uko associated-resources-for-managed-key 
--id=93777bca-baef-4070-b9b5-a2e6079df1b4 
--uko-vault=5295ad47-2ce9-43c3-b9e7-e5a9482c362b 
--output json
* Output

The command returns the output similar to the following example:

{
"total_count": 3,
"limit": 20,
"offset": 0,
"first": {
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/managed_key/5295ad47-2ce9-43c3-b9e7-e5a9482c362b/associated_resources?limit=20"
},
"last": {
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/managed_key/5295ad47-2ce9-43c3-b9e7-e5a9482c362b/associated_resources?limit=20&offset=0"
},
"previous": {
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/managed_keys?offset=80"
},
"next": {
You can retrieve the current allowlist, add entries to the allowlist, and also bulk upload IP addresses to the allowlist from the API.

More information is in the [API Reference](https://cloud.ibm.com/apidocs/cloud-databases-api)





 Removing an allowlist 

From the UI, remove an IP address or netmask from the allowlist by clicking Remove. You can also use CLI command is cdb deployment-whitelist-delete or send a DELETE request to the API endpoint. When all entries on the allowlist are removed, the allowlist is disabled and all IP addresses are accepted by your deployment.







 Allowlist Cloud Databases in your Environment 

If you use allowlists to control connections in your environment, use the following IP lists to allowlist Cloud Databases deployments. We recommend you allowlist all of the subnet ranges for the entire region that your deployments live in.



 in-che List 



 Public Subnets 



Table 1. in-che Public Subnets

 Location Region Data center Subnet First IP 

 Chennai in-che che01 169.38.95.127/27 169.38.95.97 
 Chennai in-che che01 169.38.121.159/28 169.38.121.145 
 Chennai in-che che01 169.38.132.127/25 169.38.132.1 
 Chennai in-che che01 169.38.136.255/26 169.38.136.193 
 Chennai in-che che01 169.38.73.151/29 169.38.73.145 
 Chennai in-che che01 169.38.105.79/29 169.38.105.73 







 Private Subnets 



Table 2. in-che Private Subnets

 Location Region Data center Subnet First IP 

 Chennai in-che che01 10.162.8.127/26 10.162.8.65 
 Chennai in-che che01 10.163.20.127/25 10.163.20.1 
 Chennai in-che che01 10.162.115.103/29 10.162.115.97 
 Chennai in-che che01 10.162.132.79/29 10.162.132.73
ibmcloud resource service-instance-delete mean-sample-mongodb



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).





 Related Content 



* [Text analysis with Code Engine](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-text-analysis-code-engine)
If you define both the deprecate-at and obsolete-at dates, the obsolete-at date must be after the deprecate-at date.

ibmcloud is image-update IMAGE [--deprecate-at YYYY-MM-DDThh:mm:ss+hh:mm] [--obsolete-at YYYY-MM-DDThh:mm:ss+hh:mm]

If you want to change the deprecate-at and obsolete-at date and time entries, you can run these commands again. The previous dates and times are then replaced with the new dates and times.





 Removing previously scheduled image from volume lifecycle statuses by using the CLI 

You can remove a scheduled status change by using the --reset-deprecate-at or --reset-obsolete-at options. If you use either of these options with the ibmcloud is image-update command, the date and time are removed from the image. The image is no longer scheduled for that status change.

ibmcloud is image-update IMAGE [--reset-deprecate-at] [--reset-obsolete-at]

If you use both the --reset-deprecate-at and --reset-obsolete-at options, the image status returns to available.





 Changing an image from volume lifecycle status by using the API 

You can change the lifecycle status of a IBM Cloud VPC image from volume by using the application programming interface (API). You can make an immediate status change or schedule a status change to happen later.

To make an immediate status change, use one of the following examples. For the$image_id variable, specify the ID of the custom image for the status change.

You can make an immediate status change only if a future status change is not scheduled. To remove a scheduled status change, see [Remove a scheduled custom image lifecycle status change by using the API](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc-manageschedule-ilm-reset-status-change-API). After you remove the scheduled status change, you can make an immediate status change.
You can restore a resource within 7 days after you delete it.
You can run the 'ibmcloud resource reclamations' command to check the resources that you can restore.
To irrecoverable delete the instance run the 'ibmcloud resource reclamation-delete RECLAMATION_ID' command.

When you delete a virtual server from the resource list, the server isn't deleted immediately, it stops and is marked for deletion. It is deleted after a reclamation period of seven days. During this seven-day reclamation period, you can restore the virtual server or manually trigger a deletion thru [resource reclamations](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_reclamations).







 hpvs registration-key-create 

This command creates a Hyper Protect virtual server gpg registration key. The resulting output files are required as inputs for the hpvs registration-create command, where it is used to sign the registration definition file for the deployment that uses your own image (BYOI). You need to run this command only when you do not have the gpg registration key or you have not already created the key pair, and when you want to use your own image (BYOI).

ibmcloud hpvs registration-key-create ID [--gpg-passphrase-path FILE-PATH] [-v VERBOSE]

ID
: The user ID to set for the gpg registration key.



 Command options 

--gpg-passphrase-path FILE-PATH
: Is the path for the file that contains the passphrase that is being used for the registration key. The passphrase must consist of at least 6 characters. To make sure that a new line is not appended, use echo with -n or cat with EOF. If the path is not specified, you are prompted for the passphrase.

-v, --verbose
: Set to true for verbose output.





 Example output 

$ ibmcloud hpvs registration-key-create abcdefg
Enter password>
For more information, see [Deleting an API key](https://cloud.ibm.com/docs/account?topic=account-userapikeydelete_user_key) and [Removing users from an account](https://cloud.ibm.com/docs/account?topic=account-remove).
2. You need a plan for making VPC live. This includes tasks such as:



* Updating your DNS server
* If your data syncs between classic and VPC, you will need to resync after provision.
* VPC+ Cloud Migration does not shut down or delete any of the resources that were been migrated to VPC. So, you will have two active environments. You will need to close the resources in your classic environment.
* Moving any traffic that is currently active in classic to VPC.
* If your instance has a public interface, you need to manually attach a floating IP in VPC. The VPC+ tool does not do this for you.
It MAY occasionally be used for PUT or POST requests where it is impractical to return a resource representation because of size or cost, or for GET requests where a resource exists but has an empty representation. 
 206 [Partial Content](https://datatracker.ietf.org/doc/html/rfc7233section-4.1) This code indicates that the server is delivering only part of the resource. Servers MUST use this when enabling the client to resume interrupted downloads, or to split a download into multiple simultaneous streams.<br><br>[2] 





 Requests requiring no action 

If a request attempts to put a resource into a state which it is already in, the status code SHOULD be in the 2xx range. In other words, the status code SHOULD match what would be given if a change had been required.

This may not always be practical, however. If a client makes a DELETE request for a resource that has already been deleted, the server is not required to maintain a record of the deleted resource and MAY respond with 404.

[3]







 Redirection: 3xx 



Redirection status codes

 Code Meaning Description 

 300 [Multiple Choices](https://datatracker.ietf.org/doc/html/rfc7231section-6.4.1) This code MAY be returned in the uncommon scenarios where the URI requested does not unambiguously specify a particular resource or representation of a resource. See [URI Ambiguity](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-status-codesuri-ambiguity) below. 
 301 [Moved Permanently](https://datatracker.ietf.org/doc/html/rfc7231section-6.4.2) This code SHOULD be returned when a resource's URI changes, in order to keep the previous URI from failing. When this code is returned, the server MUST also include a Location header. It indicates that the current request, and all future requests, should be directed to the URI provided in the Location header.
* To delete all unused user tags from the account:

ibmcloud resource tag-delete -a
* To delete all unused access management tags from the account:

ibmcloud resource tag-delete -a --tag-type access









 ibmcloud resource reclamations 

List reclaimed resources that can be restored or deleted:

ibmcloud resource reclamations [--resource-instance-id INSTANCE_ID]



 Command options 

--resource-instance-id
: The globally unique ID (GUID) of the resource instance





 Examples 

List all resource reclamations:

ibmcloud resource reclamations

List resource reclamations of a particular service instance:

ibmcloud resource reclamations --resource-instance-id abcd1234-ef56-486e-b293-22d6c7eb6699







 ibmcloud resource reclamation 

Show details of a resource reclamation:

ibmcloud resource reclamation RECLAMATION_ID



 Command options 

RECLAMATION_ID
: Resource reclamation ID





 Examples 

Show details of a resource reclamation:

ibmcloud resource reclamation daf12d343ef







 ibmcloud resource reclamation-restore 

Restore a reclaimed resource so that the resource is available again:

ibmcloud resource reclamation-restore ID [--comment COMMENT]



 Command options 

ID
: ID of the resource reclamation

--comment
: Comments about the action





 Examples 

Restore a resource reclamation with ID d9fendfwlw:

ibmcloud resource reclamation-restore "d9fendfwlw"

Restore a resource reclamation with ID d9fendfwlw, leave a comment of need to use for another 3 months, and show JSON output:

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
cas_required false
created_time 2022-03-04T17:08:34.406336489Z
current_version 3
custom_metadata map[key1:value1 key2:value2]
delete_version_after 0s
max_versions 10
oldest_version 0
updated_time 2022-03-08T20:06:39.585190049Z

====== Version 1 ======
Key Value
--- -----
created_time 2022-03-04T17:08:34.406336489Z
deletion_time n/a
destroyed true

====== Version 2 ======
Key Value
--- -----
created_time 2022-03-08T18:32:43.610242127Z
deletion_time 2022-03-08T20:05:08.850704454Z
destroyed false

====== Version 3 ======
Key Value
--- -----
created_time 2022-03-08T20:06:39.585190049Z
deletion_time n/a
destroyed false







 Delete the metadata and all versions of a key-value secret 

Delete the metadata and all version data of a specified key-value secret permanently. All version history is removed when you use this command.

vault kv metadata delete ibmcloud/kv/SECRET_NAME

vault kv metadata delete ibmcloud/kv/GROUP_ID/SECRET_NAME



 Prerequisites 

You need the [Manager service role](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-iam) to delete the metadata of key-value secrets.





 Command options 

-format
: Prints the output in the format that you specify. Valid formats are table, json, and yaml. The default is table.
Filtering the view of existing domains 

A list of all active domains associated with the account is displayed on the Domains page. For accounts with multiple domains, the view may be filtered to view and interact with selected domains.

Follow these steps to filter the view of existing domains.



1.  From your browser, open the [IBM Cloud® console](https://cloud.ibm.com/) and log in to your account.
2.  Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/86dadb3996e7fa2b119c2c09bda56dbc01297416/icons/icon_hamburger.svg), then click Classic Infrastructure.
3.  From the Classic Infrastructure menu, select Services > Domain Registration to open the Domains page.
4.  Select the Filter tab.
5.  Determine whether domains should be filtered by Domain Name, Expiration Date, or Lock Status. If filtering by:



*  Domain Name: Enter all or part of the domain name in the Domain Name field or select the domain name from the Domain Name list.
*  Expiration Date: Select the period of time when the domain will expire from the Expires list.
*  Lock Status: Select the applicable lock status from the Lock Status list.



6.  Click the Filter button to filter the domains listed, or click Cancel to cancel the filter options.
To delete a workspace (and all its resources), use the left navigation to navigate the workspace page. Find the workspace to be deleted and click on the overflow menu on the top right corner of the tile. Click Delete and confirm the request from the pull-down menu by typing Delete in the text field. Finally, click the red Delete button to initiate the request.





 How do I delete a single virtual server instance? 

There are two methods to delete a virtual server instance. Both deletion methods are manual processes. There is no way to delete all VSIs without deleting the workspace or deleting a subset of the virtual server instance.



* Delete a single virtual server instance from the Virtual server instances page. Click on the overflow menu (icon with 3 vertical dots) on the far right of each virtual server instance entry on the table. From the pull-down menu, click Delete to open the delete confirmation modal. Click Delete instance to initiate the deletion request. This action cannot be undone.
* Delete a single virtual server instance from the its details page. Navigate to the virtual server instance's details page by clicking on the virtual server instance name on the table on the Virtual server instances page. Find and click on the trash icon on the top right of the screen. Confirm the request by clicking Delete instance. This action cannot be undone.







 How do I open a support ticket for the Power Systems Virtual Server workspace? 

To open a support ticket, see [Getting help and support](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-help-and-support).





 What are the supported databases that I can run for SAP on Power Systems Virtual Server? 

On an AIX VM, the following databases are supported:



* IBM Db2 for LUW (Linux, UNIX, and Windows) version 10.5, or later
* Oracle Database version 12.1.0.2, or later
* SAP Adaptive Server Enterprise version 16.0 SP03, or later



On a Linux VM, the following database is supported:
input := new(s3.ListBucketsExtendedInput).SetMaxKeys(<MAX_KEYS>).SetMarker("<MARKER>").SetPrefix("<PREFIX>")
output, _ := client.ListBucketsExtended(input)

jsonBytes, _ := json.MarshalIndent(output, " ", " ")
fmt.Println(string(jsonBytes))
}

Key Values



* <MAX_KEYS> - Maximum number of buckets to retrieve in the request.
* <MARKER> - The bucket name to start the listing (Skip until this bucket).
* <PREFIX - Only include buckets whose name start with this prefix.







 Getting an extended listing with pagination 

func main() {

// Create client
sess := session.Must(session.NewSession())
client := s3.New(sess, conf)

i := 0
input := new(s3.ListBucketsExtendedInput).SetMaxKeys(<MAX_KEYS>).SetMarker("<MARKER>").SetPrefix("<PREFIX>")
output, _ := client.ListBucketsExtended(input)

for _, bucket := range output.Buckets {
fmt.Println(i, "tt", bucket.Name, "tt", bucket.LocationConstraint, "tt", bucket.CreationDate)
}

}
Show more

Key Values



* <MAX_KEYS> - Maximum number of buckets to retrieve in the request.
* <MARKER> - The bucket name to start the listing (Skip until this bucket).
* <PREFIX - Only include buckets whose name start with this prefix.







 Archive Tier Support 

You can automatically archive objects after a specified length of time or after a specified date. Once archived, a temporary copy of an object can be restored for access as needed. Please note the time required to restore the temporary copy of the object(s) may take up to 12 hours.