vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* UI
* CLI
* API
* Terraform







 Deleting a transit gateway 



 Deleting a transit gateway in the UI 

To delete an IBM Cloud® Transit Gateway, 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 Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) on the upper left of the page, then click Interconnectivity.
3. Click Transit Gateway.
4. Click the name of the transit gateway you want to delete.
5. Ensure the transit gateway has no attached connections - if it does, delete all connections. For each connection you want to delete, click the Actions menu next to it, then select Delete.
6. After the connections are removed, you can delete the transit gateway in two ways:



* From the transit gateway's details page, click the Actions menu ![Actions menu](https://cloud.ibm.com/docs-content/v1/content/6a28e4ae2660b609a18e90e1239ed772f80373d6/transit-gateway//images/overflow.png) next to the gateway you want to delete and select Delete.
* From an individual transit gateway page, select Actions > Delete.









 Deleting a transit gateway from the CLI 

To delete an existing gateway from the CLI, enter the following command:

ibmcloud tg gateway-delete|gwd GATEWAY_ID [-f, --force] [-h, --help]

Where:



* GATEWAY_ID: ID of the gateway you want to delete.
* --force | -f: Optional: Force the delete without confirmation.
* --help | -h: Optional: Get help on this command.





 Example 

This example illustrates deleting a gateway with no confirmation:
iam_serviceid_crn: crn:v1:bluemix:public:iam-identity::a/b42116849bb7e2abb0841ca25d28ee4c::serviceid:ServiceId-53f9e2a2-cdfb-4f90-b072-bfffafb68b3e
password: 581138...7d48d61
Show more



Now, the tutorial is complete. Optionally, you can delete the service credentials or service instance as shown in the steps in the next two sections.

For more information, see the [Creating and populating a simple IBM Cloudant database on IBM Cloud](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-creating-and-populating-a-simple-ibm-cloudant-database-on-ibm-cloud) tutorial. This tutorial shows you how to use an IBM Cloudant service instance from a Python application by using legacy credentials. Remember to substitute the credentials you created.





 Step 5: (Optional) Deleting service credentials 

Delete the credentials called creds_for_cs20170517a by running a command like this one.

ibmcloud resource service-key-delete creds_for_cs20170517a





 Step 6: (Optional) Deleting a service instance 

Delete the cs20170517a instance of an IBM Cloudant service by running a command like this one.

ibmcloud resource service-instance-delete cs20170517a
When you delete a domain mapping, you are removing the association of your Code Engine application with your custom domain mapping within Code Engine. This action does not delete the associated application or TLS secret.

If you delete an application that is referenced in a domain mapping, this action also deletes any custom domain mapping that is associated with the application.

When you delete a custom domain mapping, if the DNS settings of your domain are still configured, such that the CNAME points to the Code Engine project, your traffic still is routed to the Code Engine project. However, the request is answered with a 404 (not found) error message. Ensure that the associated CNAME record for the fully qualified domain name is updated in the DNS settings by the domain registrar.



 Deleting domain mappings from the console 

From the console, you can delete only domain mappings of type Custom. Domain mappings that are automatically generated by Code Engine cannot be deleted.

To delete a custom domain mapping from the console,



1. From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), go to your project.
2. From the Overview page, click Domain mappings to view a listing of defined domain mappings.
3. (Optional) Click Type to filter the domain mappings by type.
4. From the Domain mappings page, delete the custom domain mapping that you want to remove from your application. Click the Actions icon ![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.
[List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/fcee192e52fce225776143bc6ccc3a023d1d193a/databases-for-etcd/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.
Deleting a custom image template 

At any time, you can delete a bare metal server custom image template.

When you delete an image template, it can't be retrieved and is permanently removed from all data centers.

Use the following steps to delete an image.



1.  From your Devices images list, find the image that you want to delete and click the Action menu icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/icons/action-menu-icon.svg).
2.  Click Delete image.
3.  In the Delete dialog box, click Delete.
4.  The image is deleted.
* If the user owns the infrastructure account, then the infrastructure account is deleted when the user leaves. You can't continue to work with these clusters. To prevent the cluster from becoming orphaned, the user must delete the clusters before the user leaves. If the user leaves but the clusters were not deleted, you must use the ibmcloud ks credential set command to change your infrastructure credentials to the account that the cluster worker nodes are provisioned in, and delete the cluster. For more information, see [Unable to modify or delete infrastructure in an orphaned cluster](https://cloud.ibm.com/docs/containers?topic=containers-cluster_infra_errors).





5. Repeat these steps for each combination of resource groups and regions where you have clusters.







 Removing a user from your account 

If a user in your account is leaving your organization, you must remove permissions for that user carefully to ensure that you don't orphan clusters or other resources. After you remove permissions, you can remove the user from your IBM Cloud account.



1. [Check that the user's infrastructure credentials are not used](https://cloud.ibm.com/docs/containers?topic=containers-usersremoving_check_infra) for any IBM Cloud Kubernetes Service resources.
2. If you have other service instances in your IBM Cloud account that the user might have provisioned, check the documentation for those services for any steps that you must complete before you remove the user from the account.
3. [Remove the user from the IBM Cloud account](https://cloud.ibm.com/docs/account?topic=account-remove). When you remove a user, the user's assigned IBM Cloud IAM platform access roles, Cloud Foundry roles, and IBM Cloud infrastructure roles are automatically removed.
4. When IBM Cloud IAM platform permissions are removed, the user's permissions are also automatically removed from the associated predefined RBAC roles.
Repeat this step for each vSAN cluster.



4. From the Licenses page, select all the old vSAN cluster licenses and click Remove Licenses.









 Procedure to remove the temporary standard switch 

Reassign the vmnic that you temporarily used on the standard switch back to the distributed switch it was originally associated with.

Complete the following steps from the vCenter Server user interface.



1. Go to the new vCenter Server appliance.
2. Under Actions click Edit Settings.
3. For network adapter 1, browse to the name of the distributed port group that ends with -dpg-mgmt that you previously noted. Save the changes.
4. Go to the host where you deployed the new appliance. Select Hosts and Clusters > HOST > Configure > Virtual Switches. Then, click MANAGE PHYSICAL ADAPTERS for vSwitch0.
5. Select vmnic2 and click the red X to delete the adapter. Click OK. The There are no active physical network adapters for the switch. warning is displayed. Click OK.
6. Click the ... in the vSwitch0 display and then select Remove. Click OK to confirm you want to remove the switch.
7. In the same display, select the private switch and click MANAGE PHYSICAL ADAPTERS.
8. Select uplink1 and click +. vmnic2 is displayed.
9. Click OK, and then OK again to exit the dialog.









 Related links 



* [About vCenter Server upgrade](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.upgrade.doc/GUID-9ED7B32A-019F-4A97-BC58-1A9BF7D16C57.html)
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-web-analytics-options" "> --><-- <section "id="section-web-analytics-examples" "> --> Examples Get web analytics for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis web-analytics 31984fea73a15b45779fa0df4ef62f9b --recent 1d -t requests -i "cis-demo"
<-- </section "id="section-web-analytics-examples" "> --><-- </section "id="section-web-analytics" "> --><-- <section "id="section-dns-analytics" "> --> ibmcloud cis dns-analytics Get DNS analytics of the domain. ibmcloud cis dns-analytics DNS_DOMAIN_ID DIMENSION -s, --since TIME] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-dns-analytics-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.DIMENSION: The queried dimension. Valid values: queries-by-response-code, queries-by-type, queries-by-name. Required.-s, --since: Since time to now. Valid values are: 6h (6 hours ago), 12h, 1d (1 day ago), 1w (1 week ago)-i, --instance: Instance name or ID.
For instructions on creating custom roles, see [Creating custom roles](https://cloud.ibm.com/docs/account?topic=account-custom-roles).

If you want to delete an EP11 certificate, complete the following steps:

After you delete a certificate, you are not able to access any resources that are associated with the certificate. This action cannot be undone.



1. Select the EP11 certificates tab in the side menu, and find the certificate that you want to delete in the list.
2. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/action-menu-icon.svg), and then select Delete certificate.
3. Verify the name of the certificate to be deleted, and check the box to confirm the deletion.
4. Click Delete certificate.







 What's next 

To learn more about the PKCS #11 API, see

[PKCS #11 API reference](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-pkcs11-api-ref).
In your browser, open [IBM Cloud Resource list](https://cloud.ibm.com/resources). You need to log in with you IBM ID.
2. Under the Services twistie, locate the service instance you want to delete and click Delete on the Actions menu.



Choose this option carefully. If you delete a service instance, the storage associated with each node is deleted and cannot be restored. All your ledger data will be deleted.

If your service instance deletion fails, it could be because the Kubernetes cluster is not accessible. If this occurs, open a [support ticket](https://cloud.ibm.com/docs/blockchain?topic=blockchain-blockchain-supportblockchain-support-cases) to request the service instance deletion.
data "ibm_cd_toolchain" "cd_toolchain" {
toolchain_id = {toolchain_id}
}

resource "ibm_cd_toolchain_tool_pipeline" "cd_pipeline" {
toolchain_id = data.ibm_cd_toolchain.cd_toolchain.id
parameters {
name = "myUpdatedPipelineName"
}
}

For more information about tool integration resources, see the full list of supported tool integration resources in the [IBM Cloud Terraform Registry](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_toolchain).
3. Initialize the Terraform CLI.

terraform init
4. Create a Terraform execution plan. This plan summarizes all of the actions that must run to modify the tool integration.

terraform plan
5. Apply the Terraform execution plan. Terraform takes all of the required actions to modify the tool integration.

terraform apply







 Deleting a tool integration by using the console 

You can delete tool integrations from your toolchain by using the console. If you delete a tool integration from your toolchain, the deletion cannot be undone.



1. From the IBM Cloud console, click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg), and select DevOps.
2. On the Toolchains page, click a toolchain to open its Overview page. Alternatively, on the App details page in your app, click the toolchain name.
3. On the tool integration that you want to delete, click the Actions icon !
ibmcloud cis edge-functions-trigger 31984fea73a15b45779fa0df4ef62f9b 9a7806061c88ada191ed06f989cc3dac "example.net/" --name "demo-action" -i "cis-demo"







 ibmcloud cis edge-functions-trigger-delete 

Delete an Edge Functions trigger for a given domain of a service instance.

ibmcloud cis edge-functions-trigger-delete DNS_DOMAIN_ID TRIGGER_ID [-i, --instance INSTANCE]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

TRIGGER_ID
: The ID of the trigger. Required.

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





 Examples 

Delete Edge Functions trigger 9a7806061c88ada191ed06f989cc3dac.

ibmcloud cis edge-functions-trigger-delete 31984fea73a15b45779fa0df4ef62f9b 9a7806061c88ada191ed06f989cc3dac -i "cis-demo"









 Firewall 

Manipulate firewalls by using the following firewall commands.



 ibmcloud cis firewall-create 

Create a new firewall rule.

ibmcloud cis firewall-create (-t, --type Type) (--json @JSON_FILE | JSON_STRING) [-d, --domain DNS_DOMAIN_ID] [-i, --instance INSTANCE] [--output FORMAT]
[Deprecated] ibmcloud cis firewall-create (-t, --type Type) (-s, --json-str JSON_STR | -j, --json-file JSON_FILE) [-d, --domain DNS_DOMAIN_ID] [-i, --instance INSTANCE] [--output FORMAT]
<-- </section "id="section-delete-authenticated-origin-pull-certificate-examples" "> --><-- </section "id="section-delete-authenticated-origin-pull-certificate" "> --><-- </section "id="section-authenticated-origin-pull" "> --><-- <section "id="section-alert-policy" "> --> Alert policy Manage alert policies.<-- <section "id="section-list-alert-policies" "> --> ibmcloud cis alert-policy list (List) List all alert policies. ibmcloud cis alert-policy list -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-opt-list-alert-policies" "> --> Command options -i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-opt-list-alert-policies" "> --><-- <section "id="section-list-alert-policies-examples" "> --> Examples List all policies for instance cis-demo ibmcloud cis alert-policy list -i "cis-demo"
<-- </section "id="section-list-alert-policies-examples" "> --><-- </section "id="section-list-alert-policies" "> --><-- <section "id="section-show-alert-policy" "> --> ibmcloud cis alert-policy get (Show) Show the details of a given policy. ibmcloud cis alert-policy get POLICY_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-show-alert-policy-options" "> --> Command options POLICY_ID: The ID of alert policy.
Deleting a bucket-catalog pair 

To delete a bucket-catalog pair, complete the following steps:



1.  Dissociate the catalog that is associated with the bucket from the engine. For instructions, see [Dissociating a catalog from an engine](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-disso-cat-eng).
2.  In Infrastructure manager, go to the Buckets tab.
3.  Click the overflow menu and then click Deactivate.
4.  In the Confirm deactivation window, click Deactivate.
5.  Click the overflow menu and then click Remove.
6.  In the Confirm removal window, click Remove.
apiconnect.consumer_org_setting_singletonDelSpaceInitiated.delete Delete the Consumer Organization Setting object 
 apiconnect.activation_clearOrgScope.delete Clear the Activation objects 
 apiconnect.activation_delOrgScope.delete Delete the Activation object by name or ID 
 apiconnect.invitation_createConsumerOrgScope.create Create a Consumer Organization Invitation object 
 apiconnect.invitation_clearConsumerOrgScope.delete Clear the Consumer Organization Invitation objects 
 apiconnect.invitation_updateConsumerOrgScope.update Update the Consumer Organization Invitation object by name or ID 
 apiconnect.invitation_delConsumerOrgScope.delete Delete the Consumer Organization Invitation object by name or ID 
 apiconnect.invitation_regenerateConsumerOrgScope.create Regenerate the Consumer Organization Invitation 
 apiconnect.invitation_createConsumerOrgScopeSpaceInitiated.create Create a Consumer Organization Invitation object 
 apiconnect.invitation_clearConsumerOrgScopeSpaceInitiated.delete Clear the Consumer Organization Invitation objects 
 apiconnect.invitation_updateConsumerOrgScopeSpaceInitiated.update Update the Consumer Organization Invitation object by name or ID 
 apiconnect.invitation_delConsumerOrgScopeSpaceInitiated.delete Delete the Consumer Organization Invitation object by name or id 
 apiconnect.invitation_regenerateConsumerOrgScopeSpaceInitiated.create Regenerate the Consumer Organization Invitation 
 apiconnect.consumer_org_create.create Create a Consumer Organization object 
 apiconnect.consumer_org_clear.delete Clear the Consumer Organization objects 
 apiconnect.consumer_org_update.update Update the Consumer Organization object by name or ID 
 apiconnect.consumer_org_del.delete Delete the Consumer Organization object by name or ID 
 apiconnect.consumer_org_transferOwner.create Transfer owner to an associate 
 apiconnect.consumer_org_createSpaceInitiated.create Create a Consumer Organization object 
 apiconnect.consumer_org_clearSpaceInitiated.delete Clear the Consumer Organization objects
If a boot volume created as part of provisioning a virtual server instance, the volume will be deleted by default when the instance is deleted. After you confirm the delete action, the process to delete the instance and its associated vNIC, boot volume, and data begins. The delete action can take up to 30 minutes, but when the process is complete, the instance no longer appears on the virtual server instances page.





 Delete a virtual server instance using the API 

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

If the instance has a floating IP address, it must be unassociated or released before the instance is deleted. The account associated with the floating IP will continue to be charged if it is not released.

The following example deletes an instance.

curl -X DELETE "$vpc_api_endpoint/v1/instances/$instance_id?version=2021-06-22&generation=2" -H "Authorization: $iam_token"

The delete action permanently removes an instance and its connected vNIC, and data from your account. The instance boot volume is also deleted if the volume auto-delete setting is configured to be deleted when the attached instance is deleted. If an existing boot volume is attached as part of provisioning a virtual server instance, the volume is preserved by default when the instance is deleted. If a boot volume created as part of provisioning a virtual server instance, the volume will be deleted by default when the instance is deleted. After you confirm the delete action, the process to delete the instance and its associated vNIC, boot volume, and data begins. The delete action can take up to 30 minutes, but when the process is complete, the instance no longer appears on the virtual server instances page.

For more information, see the [Delete an instance](https://cloud.ibm.com/apidocs/vpcdelete-instance) in the Virtual Private Cloud API documentation.





 Toggle the auto-deletion of boot volumes attached to an instance using the UI 

By default, a boot volume created as part of provisioning a virtual server instance is deleted when the instance is deleted.
Deleting your Cloud Shell workspace ends and deletes all sessions in the workspace. All files and data within the workspace are erased. Before you delete the workspace, download any files that you want to keep.

To delete your Cloud Shell workspace, complete the following steps:



1. Download any files that you want to keep.
2. From your Cloud Shell workspace, click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/6e73868222d2673c4d974c1cf0452448e1b38054/icons/actions-icon-vertical.svg), and then select Delete.
3. In the confirmation window, click Delete. A blank page is displayed.
4. Click the Add icon ![Add icon](https://cloud.ibm.com/docs-content/v1/content/6e73868222d2673c4d974c1cf0452448e1b38054/icons/add.svg) to open a new Cloud Shell session. This action also creates a new Cloud Shell workspace.







 Working with sessions 

A Cloud Shell session is the terminal interface where you can run commands, scripts, and other tools. It's similar to the command prompt on your local machine, but it's preconfigured with the full IBM Cloud CLI and numerous [plug-ins and tools](https://cloud.ibm.com/docs/cloud-shell?topic=cloud-shell-plugins-tools) so that you can work in IBM Cloud without having to install anything. For more information about the CLI, see [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).

When you open a session, you start in your Cloud Shell workspace's home directory, /home/<user-name>. Your home directory provides a temporary place for you to work with files in Cloud Shell.