vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If the user does not have access to submit access requests for other customers, their account will be deactivated.

Manager user’s can only remove the customer they are managing from a user’s Customer Access List.

Follow these steps to remove the user’s accesses if your user role is Manager.



1. Sign into the Self-Service Portal: [https://devops.maximo.com](https://devops.maximo.com)
2. Navigate to the Access Management application.

![SSP-AM-Remove-User-Customer-1](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Remove-User-Customer-1.png)
3. Select the user’s IBMid from the List View that you want to remove the accesses from.

![SSP-AM-Remove-User-Customer-2](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Remove-User-Customer-2.png)
4. In the Customer Access List table, select the delete icon next to the customer row you want to remove the user’s access to.

![SSP-AM-Remove-User-Customer-3](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Remove-User-Customer-3.png)
5. A warning message will pop-up indicating that removing the user’s access to the customer will also remove all accesses under the customer for the user.
--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 resource-query delete --id us-east.INVENTORY.inventoryid12342





 ibmcloud schematics resource query get 

Retrieve the information of an existing IBM Cloud Schematics resource query by using a resource query ID.

Syntax

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

Command options



Schematics resource query get flags

 Flag Required / Optional Description 

 --id or -i Required The ID of the resource query that you want to retrieve. 
 --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 a resource query without an interactive command-line session. 



Example

ibmcloud schematics resource-query get --id us-east.INVENTORY.inventoryid12342





 ibmcloud schematics resource query list 

Retrieve a list of all Schematics resource queries in your account.

Syntax

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

Command options



Schematics resource query list flags

 Flag Required / Optional Description 

 --limit or -l Optional The maximum number of resource queries that you want to list. The number must be a positive integer between 1 and 200. The default value is -1. 
 --offset or -m Optional The position of the resource query in the list of resource queries. For example, if you have three resource queries in your account, the command returns these resource queries as a list with three elements. To see a specific resource query in this list, you must enter the position number that the resource query has in the list.
If you select the option to cancel the volume on its anniversary date, you can void the cancellation request before its anniversary date.
5. Click Continue.
6. Click the acknowledgment checkbox, and click Confirm.



When the volume is deleted, the request is followed by a 24-hour reclaim wait period. You can still see the volume in the console during those 24 hours. When the reclaim-period expires, the data is destroyed and the volume is removed from the console, too. However, billing for the volume stops immediately. For more information, see the [FAQs](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-file-storage-faqs).

After the Storage LUN is reclaimed, the disk is wiped, and data can't be restored. When drives are decommissioned in a data center, IBM destroys them before they are disposed of. The drives become unusable. Any data that was written to that drive becomes inaccessible.
You can remove authorized users from the Continuous Delivery service and prevent them from being added again.



* Remove the user's access in IAM to all toolchains in the resource group.
* Remove the user from the authorized user list in the Continuous Delivery service instance.
* Remove Developer access from all Git Repos and Issue Tracking repos that are attached to all of the toolchains in the resource group.



You can maintain an activity log related to authorized users. For more information about viewing, managing, and auditing service-initiated and user-initiated activities in your IBM Cloud® Continuous Delivery instances, see [IBM Cloud Activity Tracker events](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-cd-at-events). For more information about managing authorized users, see [Authorized users](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-limitations_usageauthorized_users).





 Can I manage Continuous Delivery service instances by using Terraform? 

You can use Terraform to provision, update, and de-provision instances of the Continuous Delivery service. 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), [Deleting a Continuous Delivery service instance with Terraform](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-delete_cd_service&interface=terraformdeleting_rg_terraform), and the [ibm_resource_instance resource documentation](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/resource_instance).

You cannot use Terraform to manage the list of authorized users for a Continuous Delivery service instance. You can manage the list of authorized users only by using the console.
Run 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 NAME

Where NAME is the name of the instance.

For example, to remove an instance, run the following command:

ibmcloud resource service-instance-delete logging-instance-01



For example, to remove an instance, run the following command:

ibmcloud resource service-instance-delete logdna-instance-01

Next, remove permissions that are granted to users to work with the instance that you deleted.
You can delete the existing collector and create a new one with the target scope that you want to use.
* Do I need to suspend a flow log collector before I delete it?

No, you can delete a flow log collector at any time, whether it is active or not.
* What is the instance metadata service?

The instance metadata service is free service that provides a REST API you invoke within an instance to get information about that instance. Access to the API is unavailable from outside the instance. Before you can access the metadata, the service lets you generate an instance identity access token, for accessing the metadata service. You can optionally get an IAM token from this token to access all IAM-enabled services.

The metadata service uses well-known IP address to retrieve instance metadata such as the instance name, CRN, resource groups, user data, as well as SSH key and placement group information. Use the initialization metadata to configure and launch new instances. For more information, see [About Instance Metadata for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-about).

The VPC Instance Metadata service is currently supported only on x86 systems.
* How does the metadata service work?

By calling the [metadata service APIs](https://cloud.ibm.com/apidocs/vpc-metadata-beta) from within an instance, you can get the instance's initialization data, network interface, volume attachment, public SSH key, and placement group information.

To use the metadata service, you need an instance identity access token. The instance identity token service lets you access the metadata service. For more information, see this [FAQ](https://cloud.ibm.com/docs?tab=faqsfaq-rmds-4).

The metadata service is disabled by default. You can enable it for new and existing instances in the UI, CLI, or API.
* What information can I get from the metadata service?

The metadata service provides information about your running virtual server instance: instance initialization data, network interface, volume attachment, public SSH key, and placement group information.
}







 Deleting a resource record 



 Request 

curl -X DELETE $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID/resource_records/$RECORD_ID -H "Authorization: $TOKEN"





 Response 

HTTP 204 is returned, no content in response.







 Importing bulk resource records from a DNS zone file 



 Request 

curl -X POST $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID/import_resource_records --form "file=@./bind.cfg" -H "Authorization: $TOKEN"





 Response 

{
"total_records_parsed": 17,
"records_added": 17,
"records_failed": 0,
"records_added_by_type": {
"A": 10,
"AAAA": 2,
"CNAME": 4,
"SRV": 0,
"TXT": 0,
"MX": 0,
"PTR": 1
},
"records_failed_by_type": {
"A": 0,
"AAAA": 0,
"CNAME": 0,
"SRV": 0,
"TXT": 0,
"MX": 0,
"PTR": 0
},
"message": null,
"errors": null
}







 Exporting bulk resource records to a DNS zone file 



 Request 

curl -X GET $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID/export_resource_records -o dns_records.cfg -H "Authorization: $TOKEN"





 Response 

HTTP 200 is returned with zone file content in byte format









 Using the CLI 

First use the ibmcloud dns instance-target command to set the target operating DNS Services instance.

$ ibmcloud dns instances
"url": "/v1/resource_keys/crn%3Av1%3Astaging%3Apublic%3Aibmanalyticsengine%3Aus-south%3Aa%2Fd628eae2cxxxxx229f2xxxx%3A79c757e9-xxxx-xxxx-xxxx-dff7f01xxxx%3Aresource-key%3A2278xxxx-xxxx-xxxx-xxxx-59a6da6xxxxe",
"created_at": "2021-11-30T08:48:47.909145179Z",
"updated_at": "2021-11-30T08:48:47.909145179Z",
"deleted_at": null,
"created_by": "",
"updated_by": "",
"deleted_by": "",
"source_crn": "crn:v1:staging:public:ibmanalyticsengine:us-south:a/d628eae2cxxxxx229f2xxxx:79c757e9-xxxx-xxxx-xxxx-dff7f01xxxx::",
"name": "service_key_02",
"role": "crn:v1:bluemix:public:iam::::serviceRole:Writer",
"crn": "crn:v1:staging:public:ibmanalyticsengine:us-south:a/d628eae2cxxxxx229f2xxxx:79c757e9-xxxx-xxxx-xxxx-dff7f01xxxx:resource-key:2278xxxx-xxxx-xxxx-xxxx-59a6da6xxxxe",
"state": "active",
"account_id": "d628eae2cxxxxx229f2xxxx",
You can delete the existing collector and create a new one with the target scope that you want to use.
* Do I need to suspend a flow log collector before I delete it?

No, you can delete a flow log collector at any time, whether it is active or not.
* What is the instance metadata service?

The instance metadata service is free service that provides a REST API you invoke within an instance to get information about that instance. Access to the API is unavailable from outside the instance. Before you can access the metadata, the service lets you generate an instance identity access token, for accessing the metadata service. You can optionally get an IAM token from this token to access all IAM-enabled services.

The metadata service uses well-known IP address to retrieve instance metadata such as the instance name, CRN, resource groups, user data, as well as SSH key and placement group information. Use the initialization metadata to configure and launch new instances. For more information, see [About Instance Metadata for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-about).

The VPC Instance Metadata service is currently supported only on x86 systems.
* How does the metadata service work?

By calling the [metadata service APIs](https://cloud.ibm.com/apidocs/vpc-metadata-beta) from within an instance, you can get the instance's initialization data, network interface, volume attachment, public SSH key, and placement group information.

To use the metadata service, you need an instance identity access token. The instance identity token service lets you access the metadata service. For more information, see this [FAQ](https://cloud.ibm.com/docs/faqsfaq-rmds-4).

The metadata service is disabled by default. You can enable it for new and existing instances in the UI, CLI, or API.
* What information can I get from the metadata service?

The metadata service provides information about your running virtual server instance: instance initialization data, network interface, volume attachment, public SSH key, and placement group information.
If it is enabled (green), this reserved IP is deleted automatically when the target is deleted. 
 Actions Click the Actions menu ![Actions menu](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/overflow.png) to display a menu of context-specific actions that you can take. There are 4 actions in the menu (Rename, Release, Unbind and Copy UUID for this reserved IP). 



Scroll to the Security groups section to view attached security groups. You can click Attach to attach a security group, or click the Actions menu ![Actions menu](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/overflow.png) to edit rules, or detach a security group.

At least one security group must be attached.





 Viewing details of an endpoint gateway using the CLI 

Before you begin, make sure to [set up your CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).

To view details of an endpoint gateway by using the CLI, enter the following command:

ibmcloud is endpoint-gateway ENDPOINT_GATEWAY [--json]

Where:



* ENDPOINT_GATEWAY is the ID of the endpoint gateway.
* --json formats the output in JSON format.







 Viewing details of an endpoint gateway using the API 

To view details of an endpoint gateway by using the API, follow these steps:



1. Set up your [API environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentapi-prerequisites-setup).
2. Store the following values in variables to be used in the API command:
Deleting vCenter Server with Hybridity Bundle instances 

To release the components that you ordered in a VMware vCenter Server® with Hybridity Bundle instance, delete the instance.

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 instances from the Resources page 



1. From the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server table, find the instance to delete.
3. In the Actions column, click the Delete icon. The status of the instance is changed to Deleting. When the instance is deleted successfully, the components of the instance are released, and the status of the instance is changed to Deleted.
4. If you want to delete the instance record from the IBM Cloud for VMware Solutions console, complete the following steps:



1. In the Actions column, click the Delete icon again.
2. In the Delete instance window, click OK.









 Procedure to delete instances from the instance details page
Why can't I delete my service instance? 

You might receive an error message if you try to delete a service instance that is already deleted from the cloud controller.

  What’s happening 

When you try to delete a service instance, the following error message is displayed:

> Gateway timeout

  Why it’s happening 

This problem happens if the service instance is already deleted from the cloud controller.

  How to fix it 

Create a service instance with the same service name, and connect it to your applications. Then, you can delete the service instance and the applications that use the service.
Why is it timing out when I list images? 

Listing images times out in IBM Cloud® Container Registry.

  What’s happening 

The request timed out while you attempted to list your images in the IBM Cloud console, CLI, or API.

  Why it’s happening 

The most likely cause of the timeout is that the account has many images. The vulnerability reports can't be displayed because the targeted account contains more images than Vulnerability Advisor can process.

  How to fix it 

You can run the [ibmcloud cr image-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_list) command with the --restrict option to reduce the scope of the list and increase performance. Alternatively, if you don't want to fetch vulnerability reports, use the --no-va option. For help with managing the number of images, see [Cleaning up your namespaces](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention).
"id": "f2b68dbb-c291-87df-6026-7611c324c823",
"locks": ],
"payload_available": true
}
]
},
"wrap_info": null,
"warnings": null,
"auth": null
}

A request to remove only specific locks lists the remaining locks in the response:

{
"request_id": "4d954026-68b3-6506-dc1d-5e77574fd2f0",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"secret_group_id": "default",
"secret_id": "184408d6-8264-5ff3-c308-6922ed04ad88",
"versions": [
{
"alias": "current",
"id": "f2b68dbb-c291-87df-6026-7611c324c823",
"locks":
"lock-for-app-1"
],
"payload_available": true
}
]
},
"wrap_info": null,
"warnings": null,
"auth": null
}







 List secret version locks 

List the locks that are associated with a specified secret version.

Use {version_id} in the URL path to specify the version. The aliases current or previous are also allowed.



Table 9. Lock secret request parameters

 Query parameters Description 

 limit The number of locks to retrieve. Default is 25. To retrieve a different set of items, use limit with offset to page through your available resources. 
 offset The number of locks to skip. Default is 0. By specifying offset, you retrieve a subset of locks that starts with the offset value.
One of: tpm_2, disabled.
* --resource-group-id: ID of the resource group. This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group. This name is mutually exclusive with --resource-group-id.
* --interactive, -i:
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is bare-metal-server-delete 

Delete one or more bare metal servers.

ibmcloud is bare-metal-server-delete (SERVER1 SERVER2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* SERVER1: ID or name of the server.
* SERVER2: ID or name of the server.
* --output: Specify output format, only JSON is supported. One of: JSON.
* --force, -f: Force the operation without confirmation.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is bare-metal-server-disk 

View details of a bare metal server disk.

ibmcloud is bare-metal-server-disk SERVER SERVER_DISK [--output JSON] [-q, --quiet]



 Command options 



* SERVER: ID or name of the server.
* SERVER_DISK: ID or name of the server disk.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is bare-metal-server-disk-update 

Update a bare metal server disk.
[List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/ec83e0c9f915f4acf715222aaa5b8387c028200c/databases-for-mongodb/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.
Response<Void> response = contextBasedRestrictionsService.deleteRule(deleteRuleOptions).execute();

response = context_based_restrictions_service.delete_rule(
rule_id='testString'
)

deleteRuleOptions := contextBasedRestrictionsService.NewDeleteRuleOptions(
"testString",
)

response, err := contextBasedRestrictionsService.DeleteRule(deleteRuleOptions)
if err != nil {
panic(err)
}
if response.StatusCode != 204 {
fmt.Printf("nUnexpected response status code received from DeleteRule(): %dn", response.StatusCode)
}

const params = {
ruleId: 'testString',
};

contextBasedRestrictionsService.deleteRule(params)
.then(res => {
done();
})
.catch(err => {
console.warn(err)
});







 Removing a network zone 

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. See [Updating context-based restrictions](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-update) for more information about removing a zone from a rule. Then, complete the following steps:



1. 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.