vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Ensure that you do not have any NSX objects that are expanded into the secondary instance that you want to delete.
3. Delete the secondary vCenter Server from the primary SSO (Single Sign-On) domain. For more information, see [Unregister vCenter Server from Single Sign-On](https://kb.vmware.com/s/article/2106736).
4. Demote the local domain controller Virtual Service Instance (VSI). For more information, see [Demoting domain controllers and domains](https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/demoting-domain-controllers-and-domains--level-200-).
5. Delete the secondary vCenter Server with Hybridity Bundle instance from the IBM Cloud for VMware Solutions console.
6. Repeat steps 1 - 5 for all secondary vCenter Server with Hybridity Bundle instances in your multisite configuration.
7. After you delete all secondary instances, you can also delete the primary instance from the IBM Cloud for VMware Solutions console.







 Related links 



* [Deleting vCenter Server with Hybridity Bundle instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_hybrid_deletinginstance)
* [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices)
* [Managing virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-virtual-servers)
type: NamespaceDeletionGroupVersionParsingFailure
- lastTransitionTime: "2021-05-18T17:40:31Z"
message: All content successfully deleted, may be waiting on finalization
reason: ContentDeleted
status: "False"
type: NamespaceDeletionContentFailure
- lastTransitionTime: "2021-05-18T17:40:31Z"
message: 'Some resources are remaining: tridentbackends.trident.netapp.io has 1 resource instances, tridentnodes.trident.netapp.io has 3 resource instances, tridentversions.trident.netapp.io has 1 resource instances, tridentvolumes.trident.netapp.io has 1 resource instances'
reason: SomeResourcesRemain
status: "True"
type: NamespaceContentRemaining
- lastTransitionTime: "2021-05-18T17:40:31Z"
message: 'Some content in the namespace has finalizers remaining: trident.netapp.io
in 6 resource instances'
reason: SomeFinalizersRemain
status: "True"
type: NamespaceFinalizersRemaining
phase: Terminating
2. Run the oc get command to get the resources that are pending removal. In the example output, the tridentbackends.trident.netapp.io has 1 resource instances. Repeat this step for each resource that has remaining instances listed in the message section of the namespace YAML that you retrieved earlier.

oc get <resource> -n <namespace>

Example command for the tridentbackends.trident.netapp.io resource.

oc get tridentbackends.trident.netapp.io -n trident

Example output

tbe-bhb5r

pvc-26d97ecd-c268-47ff-a2fd-a0a1a51a9e12
3. For each resource that has remaining instances, run the following kubectl patch command to remove the finalizers and delete the resource.
Really delete the service instance <instance_name> with ID crn:v1:bluemix:public:kms:us-south:a/ea988d3289c24739a0977651b46fb145:ea557753-a15b-4570-a9a3-1efefbd2d382::? [y/N] > y
OK
Service instance <instance_name> with ID crn:v1:bluemix:public:kms:us-south:a/ea988d3289c24739a0977651b46fb145:ea557753-a15b-4570-a9a3-1efefbd2d382:: is deleted successfully







 Provision a private instance 

Provision a private Key Protect instance.

Remember that a private instance accepts API requests from only private endpoints, which are inside the IBM Cloud. You cannot use the CLI with a private instance if you are outside the IBM Cloud.

ibmcloud resource service-instance-create <instance_name> kms tiered-pricing <region> -p '{"allowed_network": "private-only"}'



 Example 

After the private instance is created, a request is made to create a key. The request fails because the user does not have access to the private instance from outside the IBM Cloud.

The -p option specifies a JSON file or JSON string of parameters used to create the service instance.

 create a private service instance
$ ibmcloud resource service-instance-create <service-name> kms tiered-pricing us-south -p '{"allowed_network": "private-only"}'
Creating service instance <service-name> in resource group Default of account <account name> as <email address>...
OK
Service instance <service-name> was created.

Name: <service-name>
Delete the resource inventory definition by using the inventory ID from the IBM Cloud Schematics service. Note you can delete the location and region, resource group from where your inventory was created. Also, make sure your IP addresses are in the [allowlist](https://cloud.ibm.com/docs/schematics?topic=schematics-allowed-ipaddresses).

Syntax

ibmcloud schematics inventory delete --id ACTION_ID [--force]

Command options



Schematics inventory delete flags

 Flag Required / Optional Description 

 --id or -i Required The ID of an inventory that you want to delete. 
 --force or -f Optional Force the deletion without user confirmation. 
 --no-prompt Optional Set this flag to run the command without user prompts. 



Example

ibmcloud schematics inventory delete --id us-east.INVENTORY.inventoryid12342





 ibmcloud schematics inventory get 

Retrieve detailed information of an existing IBM Cloud Schematics inventory by using the inventory ID.

Syntax

ibmcloud schematics inventory get --id ID [--profile PROFILE] [--output OUTPUT] [--no-prompt]

Command options



Schematics inventory get flags

 Flag Required / Optional Description 

 --id or -i Required The ID of the resource inventory for which you want to list detailed information. 
 --profile or -p Optional The depth of information that you want to retrieve. Supported values are detailed and summary. The default value is summary. 
 --output or -o Optional Specify the output format. Only JSON format is supported. 
 --no-prompt Optional Set this flag to retrieve details of an inventory without an interactive command-line session. 



Example

ibmcloud schematics inventory get --id us-east.INVENTORY.inventoryid12342 --output json





 ibmcloud schematics inventory list 

Retrieve a list of all Schematics inventories in your account.

Syntax

ibmcloud schematics inventory list [--limit LIMIT] [--offset OFFSET] [--output OUTPUT]

Command options
For this code pattern you will need: * An [IBM Cloud® Platform account](https://cloud.ibm.com) * An instance of [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-provision) * Configured and operational use of IBM Cloud Object Storage SDKs for your choice of Java, Python, NodeJS, or Go; or, a configured and operational CLI client.





 Using the Console 

Before getting to the examples, there is one way to empty a bucket via the GUI at the [IBM Cloud console](https://cloud.ibm.com/): using an expiration rule on the bucket itself. For more information, please see the documentation on [deleting stale data with expiration rules](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-expiry).

After logging in to Object Storage, choose your storage instance. Then, select your bucket from the list of your buckets. To set the rule to delete the items, select Configuration from the navigation menu and click Add rule under the Expiration rule section. Set the number of days to '1' to delete all the items after one day.

deleting_items]

The process for rule completion can take up to 24 hours, and is on a set schedule. Please take this into consideration when applying this technique.





 CLI Client Examples 

There are many tools available to help users make the most of Object Storage and the following CLI clients offer simple ways of emptying buckets.

Sample instructions are provided for using a client application or command line once your CLI client has been configured and is operational.



 rClone example 

The rclone tool is typically used to keep directories synchronized and for migrating data between storage platforms. You can learn more from the documentation on [!using rclone](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-rclone).

rclone purge {remote}:{path} [flags]





 Minio example
"single_site_location": null,
"storage_class": "standard",
"timeouts": null
},
"sensitive_values": {
"activity_tracking": ],
"archive_rule": ],
"expire_rule": ],
"metrics_monitoring": ],
"retention_rule": ]
}
},
{
"address": "module.instance_config.ibm_cos_bucket.bad_resource_cos_bucket_missing_all_configuration1]",
"mode": "managed",
"type": "ibm_cos_bucket",
"name": "bad_resource_cos_bucket_missing_all_configuration",
"index": 1,
"provider_name": "registry.terraform.io/ibm-cloud/ibm",
"schema_version": 0,
"values": {
"activity_tracking": ],
"allowed_ip": null,
"archive_rule": ],
"cross_region_location": null,
"endpoint_type": "public",
"expire_rule": ],
"force_delete": true,
"key_protect": null,
"metrics_monitoring": ],
"region_location": "us-south",
"retention_rule": ],
"single_site_location": null,
"storage_class": "standard",
"timeouts": null
},
"sensitive_values": {
"activity_tracking": ],
"archive_rule": ],
"expire_rule": ],
"metrics_monitoring": ],
"retention_rule": ]
}
}
],
"address": "module.instance_config"
}
]
}
},
"resource_changes": [
{
kp.Error: correlation_id='59578794-2b5b-48ca-9074-bbe23760d94a', msg='Unauthorized: The user does not have access to the specified resource'

 delete the private service instance
$ ibmcloud resource service-instance-delete <service-name>
Deleting service instance <service-name> in resource group Default under account <account name> as <email address>...
Really delete the service instance <service-name> with ID crn:v1:bluemix:public:kms:us-south:a/ea988d3289c24739a0977651b46fb145:a152eee4-262e-4a39-ae13-a71b9882dcb6::? [y/N] > y
OK
Service instance <service-name> with ID crn:v1:bluemix:public:kms:us-south:a/ea988d3289c24739a0977651b46fb145:a152eee4-262e-4a39-ae13-a71b9882dcb6:: is deleted successfully







 Deleting an instance with existing keys 

You cannot delete a service instance that contains keys.



 Example 

$ ibmcloud resource service-instance-delete <instance_name>
Deleting service instance <instance_name> in resource group Default under account <account name> as <email address>...
Really delete the service instance <instance_name> with ID crn:v1:bluemix:public:kms:us-south:a/ea988d3289c24739a0977651b46fb145:a152eee4-262e-4a39-ae13-a71b9882dcb6::? [y/N] > y
FAILED
Error Code: RC-ServiceBrokerErrorResponse
* KEY_EXPIRED_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-expired-err)
* KEY_IMPT_REQ_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-impt-req-err)
* KEY_INVALID_STATE_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-invalid-state-err)
* KEY_PAYLOAD_REQ_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-payload-req-err-message)
* KEY_RESTORE_EXPIRED - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-restore-expired)
* KEY_ROOT_REQ_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-root-req-err)
* KEY_ROOT_REQ_REG_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-root-req-reg-err)
* KEY_ROTATION_NOT_PERMITTED - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-rotation-not-permitted)
* KEY_VERSION_INVALID - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-version-invalid)
"collectionType": "application/vnd.ibm.kms.registration+json",
"collectionTotal": 1
},
"resources": [
{
"keyId": "string",
"resourceCrn": "crn:v1:bluemix:public:<service-name>:<region>:a/<account-id>:<service-instance>:bucket:<bucket-name>",
"createdBy": "string",
"creationDate": "2010-01-12T05:23:19+0000",
"updatedBy": "string",
"lastUpdated": "2010-01-12T05:23:19+0000",
"description": "string",
"preventKeyDeletion": true,
"keyVersion": {
"id": "string",
"creationDate": "2010-01-12T05:23:19+0000"
}
}
]
}

The following table describes the properties of a registration.



Table 6. Properties that are associated with a registration

 Parameter Description 

 keyID The ID that identifies the root key that is associated with the cloud resource. 
 resourceCrn The Cloud Resource Name (CRN) that represents the cloud resource, such as a Cloud Object Storage bucket, that is associated with the key. 
 createdBy The unique identifier for the resource that created the registration. 
 creationDate The date the registration was created. 
 updatedBy The unique identifier for the resource that updated the registration. 
 lastUpdatedDate The date the registration was created. 
 description A description for the registration. 
 preventKeyDeletion A boolean that determines whether Hyper Protect Crypto Services must prevent deletion of the root key. If true, the associated resource is nonerasable due to a retention policy, and the Hyper Protect Crypto Services key that is encrypting the resource cannot be deleted. 
 keyVersion The version of the root key that's protecting the cloud resource. 





 Listing registrations for a specific root key with the API
Deleting resource instances by using Terraform 

Use the following steps to delete resource instances by using Terraform.



1. You can delete a resource instance by removing the following code block from your terraform file. You must have created the resource_instance using the terraform file.

data "ibm_resource_group" "group" {
name = "test"
}

resource "ibm_resource_instance" "resource_instance" {
name = "test"
service = "cloud-object-storage"
plan = "lite"
location = "global"
resource_group_id = data.ibm_resource_group.group.id
tags = ["tag1", "tag2"]

//User can increase timeouts
timeouts {
create = "15m"
update = "15m"
delete = "15m"
}
}

For more information, see the argument reference details on the [Terraform Resource Management](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/resource_instance) page.
2. After you finish building your configuration file, initialize the Terraform CLI. For more information, see [Initializing Working Directories](https://www.terraform.io/cli/init).

terraform init
3. Provision the resources from the main.tf file. For more information, see [Provisioning Infrastructure with Terraform](https://www.terraform.io/cli/run).



1. Run terraform plan to generate a Terraform execution plan to preview the proposed actions.

terraform plan
2. Run terraform apply to create the resources that are defined in the plan.

terraform apply





You can also delete a resource instance by running the following terraform destroy command.

terraform destroy -target RESOURCE_TYPE.NAME -target RESOURCE_TYPE2.NAME
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. This action is called cryptoshredding.

Cryptoshredding is a destructive action. When the key is deleted, your data is unrecoverable even from a soft delete state.





 Backups Removal 

Backups cannot be manually deleted. However, if you delete your deployment, its backups are deleted automatically.





 Reenabling from a soft delete
* UI
* CLI
* API
* Terraform







 Deleting a resource group 

You can't delete the default resource group that's added to your account. Besides the default one, you can only delete a resource group if it doesn't contain any resources.



 Deleting a resource group in the console 

To delete a resource group that doesn't contain resources and is not your default, complete the following steps:



1. In the IBM Cloud console, go to Manage > Account > Account resources > Resource groups.
2. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Delete.







 Deleting a resource group by using the CLI 

To delete a resource group that doesn't contain resources and is not your default, run the [ibmcloud resource group-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_group_delete). For example, delete resource group example-group:

ibmcloud resource group-delete example-group -f





 Deleting a resource group by using the API 

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



* Curl
* Java
* Python
* Go
* Node



curl -X DELETE https://resource-controller.cloud.ibm.com/v2/resource_groups/09f8c1c0742c493f80baaf7835212345 -H 'Authorization: Bearer <IAM_TOKEN>'
-H 'Content-Type: application/json'
ibmcloud resource service-alias-update ALIAS_NAME [-n, --name NEW_NAME] [-t, --tags TAGS] [-p, --parameters @JSON_FILE | JSON_STRING ]



 Command options 

ALIAS_NAME (required)
: Name of the service alias

-n, --name
: New name of the service alias.

-t, --tags
: Tags list.

-p, --parameters
: Parameters JSON file or JSON string.

-f, --force
: Force update without user confirmation.





 Examples 

Update service alias my-service-alias, change its name to new-service-alias:

ibmcloud resource service-alias-update my-service-alias -n new-service-alias







 ibmcloud resource service-alias-delete 

Delete a service alias.

ibmcloud resource service-alias-delete ALIAS_NAME [-f, --force]



 Command options 

ALIAS_NAME (required)
: Name of the service alias

-f, --force
: Force deletion without confirmation





 Examples 

Delete service alias my-service-alias:

ibmcloud resource service-alias-delete my-service-alias







 ibmcloud resource search 

Search resources by using Lucene query syntax.

ibmcloud resource search LUCENE_QUERY [-o, --offset OFFSET] [-l, --limit LIMIT] [-s, --sort-by (name, family, region, type, crn)] [-p, --provider PROVIDER] [-ir, --is-reclaimed (false, true, any)] [--output FORMAT]



 Command options 

-ir, --is-reclaimed
: Search for account resources that have been reclaimed. By default the search returns only active resources, however you can set is-reclaimed to any to search for resources whether they have been reclaimed or not. Set this option to true to apply the search criteria only to reclaimed resources. Set this option to false to search only for active resources. false is the default behavior.

-o, -offset
: Starting resource position number
{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).





 Deleting a Continuous Delivery service instance with Terraform 



1. Locate the Terraform file (for example, main.tf) that contains the resource block for the existing service instance. For more information about using Terraform with Continuous Delivery, see [Creating a Continuous Delivery service instance with Terraform](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-create_cd_service&interface=terraformcreate_cd_service_terraform).

The resource in the following example describes an existing Continuous Delivery service instance.

data "ibm_resource_group" "group" {
name = "default"
}

resource "ibm_resource_instance" "cd_service_instance" {
name = "my CD service instance"
service = "continuous-delivery"
plan = "lite"
location = "us-south"
resource_group_id = data.ibm_resource_group.group.id
}
2. Remove the resource block from your Terraform file.
3. Initialize the Terraform CLI.

terraform init
4. Create a Terraform execution plan. This plan summarizes all of the actions that must be run to delete the Continuous Delivery service instance.

terraform plan
5. Apply the Terraform execution plan. Terraform takes all of the required actions to delete the Continuous Delivery service instance.

terraform apply







 Restoring a deleted service instance 

After you delete an instance of the Continuous Delivery service, you can restore the deleted service instance within the data retention period of seven days.
,
"resources": ...],
...
"last_modified_at": "2021-04-09T14:36:30.505Z",
"last_modified_by_id": "IBMid-310000JVN5",
"last_permit_at": null, <-- IAM has no record of this policy ever granting a permit decision
"last_permit_frequency": 0,
"state": "active"
},
{
"id": "11155157-afb3-4792-9ebd-b1f5547be224",
"type": "access",
"subjects": ...],
"roles": ...],
"resources": ...] ! ! ! ! ! ,
...
"last_modified_at": "2019-05-09T15:28:07.045Z",
"last_modified_by_id": "IAM",
"last_permit_at": "2021-04-20T19:45:44.058Z",
"last_permit_frequency": 137, <-- it has been used this many times since IAM started keeping track
"state": "active"
},
...
<-- </section "class="ph" id="section-iam-audit-policies-list-api" "> --><-- <section "class="ph" id="section-iam-audit-policies-delete" "> --> Deleting unused policies by using the API You identified one or more policies that have not been used to grant access in a while.
For more information, see [Manually removing the DNS entries](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingservicesvc_deletingservices-DNS-entries).







 Related links 



* [Ordering Entrust CloudControl](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-entrust-cc_ordering)
* [Managing Entrust CloudControl](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managing-entrust-cc)
* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
* [FAQ](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions)
* [Entrust website](https://www.entrust.com/)