vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [IBM Cloud Data security and privacy terms](https://www.ibm.com/support/customer/csol/terms/)



For more information about how to delete a deployment of the service from Cloud Pak for Data as a Service, see [Deleting a deployment](https://dataplatform.cloud.ibm.com/docs/content/wsj/analyze-data/ml-deploy-delete.html?audience=wdp).





 Deleting an installed service instance IBM Cloud Pak for Data 

Only the owner or an Administrator of the provisioned service instance can delete it.

To deprovision a service instance of Discovery for IBM Cloud Pak for Data, complete the following steps:



1. From the IBM Cloud Pak for Data web client menu, click Services > Instances.
2. Find your service instance, and then click the menu icon and choose Delete.



For more information about how to uninstall the service, see [Uninstalling Discovery](https://www.ibm.com/docs/SSQNUZ_4.5.x/svc-discovery/discovery-uninstall.html).
Log in to the [IBM Cloud console](https://cloud.ibm.com/). From the menu bar, select Manage > Access (IAM).
2. Click the Users page, and then click the name of the user that you want to remove permissions from.
3. Click the Cloud Foundry access tab.



* To remove the user's space role



1. Expand the table entry for the organization that the space is in.
2. In the table entry for the space role, click the actions menu and select Edit space role.
3. Delete a role by clicking the close button.
4. To remove all space roles, select No space role in the drop-down list.
5. Click Save role.



* To remove the user's organization role



1. In the table entry for the organization role, click the actions menu and select Edit organization role.
2. Delete a role by clicking the close button.
3. To remove all organization roles, select No organization role in the drop-down list.
4. Click Save role.











 Remove classic infrastructure permissions 

You can remove IBM Cloud infrastructure permissions for a user by using the IBM Cloud console.

Classic infrastructure permissions apply only to classic clusters. For VPC clusters, see [Granting user permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources).



1. Log in to the [IBM Cloud console](https://cloud.ibm.com/). From the menu bar, select Manage > Access (IAM).
2. Click the Users page, and then click the name of the user that you want to remove permissions from.
3. Click the Classic infrastructure tab, then click the Permissions, Devices, or VPN subnets tabs.
4. In each tab, deselect specific permissions.
5. To save your changes, click Set and Save. Permissions are downgraded after a few minutes.
To delete the watsonx.data instance, see [Deleting watsonx.data instance](https://cloud.ibm.com/watsonxdata?topic=watsonxdata-delete_lh).
* How can I manage IAM access for watsonx.data?

IBM Cloud® Identity and Access Management (IAM) controls access to watsonx.data service instances for users in your account. Every user that accesses the watsonx.data service in your account must be assigned an access policy with an IAM role. For more information about IAM access for watsonx.data, see [Managing IAM access for watsonx.data](https://cloud.ibm.com/watsonxdata?topic=watsonxdata-iam).
* How can I add and remove the users?

To add or remove users in a component, see [Managing user access](https://cloud.ibm.com/watsonxdata?topic=watsonxdata-manage_access).
* How is the access control for users provided?

To provide access control for users to restrict unauthorized access, see [Managing data policy rules](https://cloud.ibm.com/watsonxdata?topic=watsonxdata-data_policy).



Developer tools App Configuration



* How to create an App Configuration instance?



1. Log in to your IBM Cloud account.
2. In the IBM Cloud catalog, search App Configuration and select App Configuration. The service configuration screen opens.
3. In the Create tab, select the location that represents the geographic area (Region) where you want to provision your instance.
4. Select a Pricing plan.
5. Configure your resource by providing a Service name for your instance, or use the preset name.
6. Select a Resource group.
7. Optional: Add Tags to help you to identify and organize the instance in your account. If your tags are billing related, consider writing tags as key: value pairs to help group-related tags, such as costctr: 124.
8.
After all subnets and public gateways in the VPC are deleted, run the following command to delete the VPC, where $vpc is the ID of the VPC you are deleting.

ibmcloud is vpc-delete $vpc

The status of the VPC changes to deleting immediately, but it might take a few minutes until the VPC is deleted and no longer appears in the list query results.







 Deleting a VPC by using the REST APIs 

Deleting an IBM Cloud® Virtual Private Cloud by using the REST APIs follows the same general steps in the [deleting](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-deleting) process as deletion by using the [CLI](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-deleting-using-cli).

The following steps are the main parts in the process:



1. Find all subnets in the VPC that you want to delete.
2. Delete each subnet in the VPC, which means:



* Delete all VPN gateways in the subnet.
* Delete all Load Balancers in the subnet.
* Delete all network interfaces of the instances in the subnet.
* Delete the subnet.



3. Delete all public gateways in the VPC.
4. Delete the VPC.



The following sections provide some example API calls that you can run to delete a VPC.



 Step 1: Find all subnets in 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:

Add | json_pp or | jq after the curl command to get a readable JSON string.
Prerequisites 

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





 Command options 

IMAGE
: The name of the image that you want to delete. You can delete multiple images at the same time by listing each image in the command with a space between each name. You can identify images by using either the digest <dns>/<namespace>/<repo>@<digest> or by tag <dns>/<namespace>/<repo>:<tag>. Where <dns> is the domain name, <namespace> is the namespace, <repo> is the repository, <digest> is the digest, and <tag> is the tag.

Images are stored in the trash for 30 days.

To find the names of your images, run one of the following commands:



* To identify your image by digest, run the ibmcloud cr image-digests command. Combine the content of the Repository column (repository) and the Digest column (digest) separated by an at (@) symbol to create the image name in the format repository@digest.
* To identify your image by tag, run the ibmcloud cr image-list command. Combine the content of the Repository column (repository) and Tag column (tag) separated by a colon (:) to create the image name in the format repository:tag. If a tag is not specified in the image name, the image that is tagged latest is deleted by default.







 Example 

Delete the image us.icr.io/birds/bluebird:1.

ibmcloud cr image-rm us.icr.io/birds/bluebird:1







 ibmcloud cr image-tag 

Add a [tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag) that you specify in the command to an existing image, copy the tag to another repository, or copy the tag to a repository in a different namespace.
1. Log in to the [IBM Cloud console](https://cloud.ibm.com/). From the menu bar, select Manage > Access (IAM).
2. Click the Users page, and then click the name of the user that you want to remove permissions from.
3. Click the Cloud Foundry access tab.



* To remove the user's space role



1. Expand the table entry for the organization that the space is in.
2. In the table entry for the space role, click the actions menu and select Edit space role.
3. Delete a role by clicking the close button.
4. To remove all space roles, select No space role in the drop-down list.
5. Click Save role.



* To remove the user's organization role



1. In the table entry for the organization role, click the actions menu and select Edit organization role.
2. Delete a role by clicking the close button.
3. To remove all organization roles, select No organization role in the drop-down list.
4. Click Save role.











 Remove classic infrastructure permissions 

You can remove IBM Cloud infrastructure permissions for a user by using the IBM Cloud console.

Classic infrastructure permissions apply only to classic clusters. For VPC clusters, see [Granting user permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources).



1. Log in to the [IBM Cloud console](https://cloud.ibm.com/). From the menu bar, select Manage > Access (IAM).
2. Click the Users page, and then click the name of the user that you want to remove permissions from.
3. Click the Classic infrastructure tab, then click the Permissions, Devices, or VPN subnets tabs.
4. In each tab, deselect specific permissions.
5. To save your changes, click Set and Save.
You can have a maximum of 15 (one primary and 14 secondary) instances that are deployed in a multisite configuration.

Deleting vCenter Server instances that are part of a multisite configuration requires special planning. For more information, see [Deleting vCenter Server instances in a multisite configuration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletinginstance_multi).





 Related links 



* [Microsoft Active Directory Trusts supported with VMware vCenter single sign-on](https://kb.vmware.com/s/article/2064250)
(Optional) Deleting a service instance Delete an instance by running a command like this one:

ibmcloud resource service-instance-delete <INSTANCE_NAME>







 The --parameters parameter 

The service-instance-create command supports a -p flag, which allows JSON-formatted parameters to be passed to the provisioning process. Some parameter values are Cloud Resource Names (CRNs), which uniquely identify a resource in the cloud. All parameter names and values are passed as strings.

For example, if a database is being provisioned from a particular backup and the new database deployment needs a total of 9 GB of memory across three members, then the command to provision 3 GBs per member looks like:

ibmcloud resource service-instance-create databases-for-mongodb <SERVICE_NAME> standard us-south -p '{
"backup_id": "crn:v1:blue:public:databases-for-mongodb:us-south:a/54e8ffe85dcedf470db5b5ee6ac4a8d8:1b8f53db-fc2d-4e24-8470-f82b15c71717:backup:06392e97-df90-46d8-98e8-cb67e9e0a8e6",
"members_memory_allocation_mb": "3072"
}'







 Provisioning through the Resource Controller API 

Follow these steps to provision using the [Resource Controller API](https://cloud.ibm.com/apidocs/resource-controller/resource-controller).



1. Obtain an [IAM token from your API token](https://cloud.ibm.com/apidocs/resource-controller/resource-controllerauthentication).
2. You need to know the ID of the resource group that you would like to deploy to. This information is available through the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_groups).

Use a command like:

ibmcloud resource groups
Uninstalling your workspace or resources 

You can uninstall WebSphere Application Server from the IBM Cloud Schematics workspace. Uninstallation deletes all the VSIs, VPC, and related artifacts that were set up during the installation.



  Uninstall from the Schematics workspace 



1.  Log in to IBM Cloud and [find the Schematics workspace](https://cloud.ibm.com/schematics/workspaces) that was created during the installation.
2.  Click Actions > Destroy. This will delete all the VSIs, VPC, and related artifacts that were set up during the installation. If you created or changed any infrastructure configuration, then you might need to clean up the artifacts manually.
3.  You can also delete the workspace by clicking Actions > Delete workspace.
* [Before you begin](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wksprerequisites-delete)
* [Deleting the workspace through UI](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wksdelete-wks-ui)



* [Verifying workspace delete](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wksverify-wks-delete-ui)



* [Deleting the workspace through CLI](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wksdelete-wks-cli)



* [Verifying workspace delete](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wksverify-wks-delete-cli)



* [Deleting the workspace through API](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wksdelete-wks-api)



* [Verifying workspace delete](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wksverify-wks-delete-api)



* [Deleting the workspace with Terraform](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wksdelete-wks-terraform)
* [Next steps](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wkssch-delete-wks-nextsteps)
Viewing on-premises VMware HCX instances 

Use this procedure to view the on-premises VMware® HCX™ instances that you ordered for on-premises use and information about them.



  Procedure to view on-premises VMware HCX instances 

From the IBM Cloud® for VMware Solutions console, click Licenses from the left navigation pane and scroll down to the On-premises HCX activation keys table to view information about the instances that you ordered.



Table 1. On-premises HCX activation keys

 Item            Description                                                         

 Name            The name of the instance.                                           
 Activation key  The activation key of the on-premises HCX instance.                 
 Creation time   The date and time when the instance was created.                    
 Status          The status of the instance.                                         
 Actions         Click the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg) to delete the instance.      



The instance can have different statuses.



Table 2. On-premises HCX instances status descriptions

 Status     Description                     

 Modifying  The instance is being created.  
 Installed  The instance is ready to use.   
 Removing   The instance is being deleted.  







  Related links 



*  [Ordering on-premises HCX instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-standalone_orderingserviceinstances)
*  [Deleting on-premises HCX instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-standalone_deletingserviceinstances)
*  [Glossary of HCX terms](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_glossary)
*  [VMware Hybrid Cloud Extension documentation](https://cloud.vmware.com/vmware-hcx/resources)
strategy = "host_spread"
name = "my-placement-group-modified"
resource_group = data.ibm_resource_group.default.id
}





 Deleting a placement group with the UI 

You can delete a placement group in your IBM Cloud VPC by using the IBM Cloud console. A placement group can't be deleted if instances are attached to it. All instances must be removed first. For more information about deleting a virtual private cloud instance and its associated resources, see [Deleting a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting).

Use the following steps to delete a placement group:



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Placement Groups.
2. Select the placement group and click Delete.
3. A confirmation message is displayed. Click Delete.







 Deleting a placement group with the CLI 

You can delete a placement group in your IBM Cloud VPC by using the command-line interface (CLI). A placement group can't be deleted if instances are attached to it. All instances must be removed first. For more information about deleting a virtual private cloud instance and its associated resources, see [Deleting a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting).

To delete placement group by using the CLI, use the ibmcloud is placement-group-delete command. Specify the placement group ID.

The following example deletes a placement group named PLACEMENT_GROUP.

ibmcloud is placement-group-delete PLACEMENT_GROUP --output JSON
* For more information on deleting a floating IP, see [Deleting VPC resources by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting-using-console), [Deleting VPC resources by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting-using-cli), or [Deleting VPC resources by using the API](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting-using-api).



* network-acl



* For more information, see [About network ACLs](https://cloud.ibm.com/docs/vpc?topic=vpc-using-acls). -->



* load-balancer



* For more information, see:



* [Creating a network load balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-ui-creating-network-load-balancer&interface=ui) and [Deleting an IBM Cloud Network Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-deleting&interface=ui).
* [Creating an IBM Cloud Application Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancer&interface=ui) and [Deleting an IBM Cloud Application Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-alb-deleting&interface=ui).





* volume



* For more information, see [Creating block storage volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage) and [Delete a block storage data volume](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=uidelete).
* UI
* CLI
* API







 Deleting a workspace 

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



 Deleting a workspace using the UI 



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







 Deleting a workspace using the CLI 

Run the following command to delete your workspace:

ibmcloud schematics workspace delete --id <WORKSPACE_ID>

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





 Deleting a workspace using the API 



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



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



4.
Deleting vCenter Server with Hybridity Bundle instances in a multisite configuration 

There are special considerations to be aware of before you plan to delete VMware vCenter Server® with Hybridity Bundle instances that are part of a multisite configuration.

When you delete a vCenter Server with Hybridity Bundle instance, the following components are released sequentially:



1. All deployed services
2. Support and Services fee
3. VMware® product licenses
4. VMware ESXi™ servers
5. Subnets
6. VLANs



Any VLANs that have your own resources added to them, such as gateways, Veeam® servers, and so on, are not deleted. In addition, any existing VLANs that you own, outside of IBM Cloud® for VMware Solutions, are not deleted.

Because of resource dependencies, the components in your instance are not released immediately when you delete the instance. For example, the VLANs and the VLAN primary subnets cannot be deleted until the ESXi servers are fully reclaimed by the IBM Cloud infrastructure, which happens at the end of the IBM Cloud infrastructure billing cycle. At the end of the billing cycle, which is typically 30 days, the subnets and VLANs are deleted and the instance deletion is completed.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted instance.



 Procedure to delete vCenter Server with Hybridity Bundle instances in a multisite configuration 



1. Delete all services from the secondary vCenter Server with Hybridity Bundle instance.
2. 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).
In the IBM Cloud console, go to Manage > Context-based restrictions, and select Network zones.
2. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) in the row that contains the network zone, and click Remove.







 Removing a network zone by using the CLI 

Removing a network zone removes the set of allowed network locations from which an access request is created. If a network zone is added to a rule, you first have to remove the zone from the rule. For more information about removing a zone from a rule, see [Updating context-based restrictions](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-update) . Then, complete the following steps:



1. Retrieve the zone ID for the network zone that you want to delete by using the [contxt-based restrictions zones](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-zones-command) command. You can narrow the results of the list by specifying the name of the zone.

ibmcloud cbr zones --name "Example zone"
2. Delete the network zone for the specified zone ID by using the [cbr zone-delete](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-zone-delete-command) command.

ibmcloud cbr zone-delete 65810ac762004f22ac19f8f8edf70a34







 Removing a network zone by using the API 

Removing a network zone removes the set of allowed network locations from which an access request is created. If a network zone is added to a rule, you first have to remove the zone from the rule.