vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Remove user.



Any resources that are created by the user remain in the account, but any IBM Cloud API keys that the user created are removed. The user no longer has access to work with the resources they created. The account owner or an administrator for the service or service instance can assign other users to work with the resources, or delete them from the account.

If you get an error message that states a classic infrastructure user can't be removed, make sure that any descendants in the user hierarchy for that user are [assigned a new parent](https://cloud.ibm.com/docs/account?topic=account-iam-user-settingupdate-parent), [disabled in the account](https://cloud.ibm.com/docs/account?topic=account-status), or deleted. Then, you can try again.





 Removing a user from an account by using the CLI 

To remove a user from an account, run the following command:

ibmcloud account user-remove USER_ID [-c ACCOUNT_ID] [-f, --force]

For command options, see [Managing accounts, users, and Cloud Foundry orgs](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_accountibmcloud_account_user_remove) CLI commands.





 Removing a user from an account by using the API 

To remove a user from an account, call the [User Management API](https://cloud.ibm.com/apidocs/user-management?code=javaremove-user) as shown in the following sample request. Replace variables with the user's IAM ID. You must use a user token for authorization. Service IDs can't remove users from an account.



* Curl
* Java
* Python
* Go
* Node
* ibmcloud is key-create my-key "ssh-ed25519 AAAAC3NzaC1lZDI1NTE6AAAAID/R2T8h6CPvZr/InxpBrxh8bmG2RTyB8vzUTvOtQhaJ test@example.com" --key-type ed25519
* ibmcloud is key-create my-key @/tmp/my_id_ed25519.pub --key-type ed25519
* ibmcloud is key-create my-key @/tmp/my_id_ed25519.pub --key-type ed25519 --output JSON







 Command options 



* KEY_NAME: ID or name of the key.
* KEY: key|@key-file. The public SSH key to import into the system.
* --key-type: The crypto-system used by this key. Default is rsa. One of: rsa, ed25519.
* --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.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is key-delete 

Delete one or more keys.

ibmcloud is key-delete (KEY1 KEY2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command examples 



* ibmcloud is key-delete e9e7655e-0000-0000-0000-0000001a957a --output JSON
* --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.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is key-delete 

Delete one or more keys.

ibmcloud is key-delete (KEY1 KEY2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command examples 



* ibmcloud is key-delete e9e7655e-0000-0000-0000-0000001a957a --output JSON
* ibmcloud is key-delete e9e7655e-0000-0000-0000-0000001a957a -f







 Command options 



* KEY1: ID or name of the key.
* KEY2: ID or name of the key.
* --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 key-update 

Update the name of a key.

ibmcloud is key-update KEY --name NEW_NAME [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is key-update e9e7655e-0000-0000-0000-0000001a957a --name my-new-name
This file is usually located at $HOME/.ssh/known_hosts (Mac OS or Linux) or at %HOMEPATH%.sshknown_hosts (Windows). This value is optional.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

The following command creates a Git access secret called github for host github.com and authenticates with an SSH key located at /<filepath>/.ssh/id_rsa, where <filepath> is the path on your system.

ibmcloud ce repo create -n github --key-path /<filepath>/.ssh/id_rsa --host github.com





 Example output 

Creating Git access secret github...
OK







 ibmcloud ce repo delete 

Delete a Git repository access secret.

ibmcloud ce repo delete --name NAME [--force] [--ignore-not-found] [--quiet]



 Command Options 

--name, -n
: The name of the Git repository access secret. This value is required.

--force, -f
: Force deletion without confirmation. This value is optional. The default value is false.

--ignore-not-found, --inf
: If not found, do not fail. This value is optional. The default value is false.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

ibmcloud ce repo delete --name github





 Example output
For platform API keys that represent your user identity you can prevent the API key from being deleted by locking it. A locked API key is indicated by the Locked icon ![Locked icon](https://cloud.ibm.com/docs-content/v1/content/814aeaf04800bb4f74ea1c057d4abb166a5f357a/account/images/locked.svg).



 Locking and unlocking an API key from the UI 



1. In the IBM Cloud console, go to Manage > Access (IAM) > API keys.
2. Identify the row of the API key that you want to lock, and click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/814aeaf04800bb4f74ea1c057d4abb166a5f357a/icons/action-menu-icon.svg) > Lock.



You can unlock your API key at any time to update or remove the API key from your account. Select the API key from the table that you want to unlock and click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/814aeaf04800bb4f74ea1c057d4abb166a5f357a/icons/action-menu-icon.svg) > Unlock.





 Locking and unlocking an API key by using the CLI 

To lock an API key, use the following command:

ibmcloud iam api-key-lock (NAME|UUID) [-f, --force]

Prerequisites: Endpoint, Login

Command options:

NAME
: The name of the API key to be locked, exclusive with the UUID option.

UUID
: The UUID of the API key to be locked, exclusive with the NAME option.

-f, --force
: Force lock without confirmation.

Examples:

Lock the API key named test-api-key:
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) to open a list of options.
5. Click Lock API key.



You can unlock your API key at any time to update, delete, or add an access policy, or to remove the API key.





 Locking or unlocking a service ID API key with the CLI 

For API keys that represent the identity of the service ID, you can prevent the API key from being deleted by locking it. A locked API key is indicated by the Locked icon ![Locked icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/account/images/locked.svg) in the UI. To lock a service ID API key, use the following command:

ibmcloud iam service-api-key-lock (APIKEY_NAME|APIKEY_UUID) (SERVICE_ID_NAME|SERVICE_ID_UUID) [-f, --force]

Prerequisites: Endpoint, Login, Target

Command options:

APIKEY_NAME
: The name of the API key, exclusive with the APIKEY_UUID option. Required.

APIKEY_UUID
: The UUID of the API key, exclusive with the APIKEY_NAME option. Required.

SERVICE_ID_NAME
: The name of the service ID, exclusive with the SERVICE_ID_UUID option. Required.

SERVICE_ID_UUID
: The UUID of the service, exclusive with the SERVICE_ID_NAME option. Required.

-f, --force
: Lock without confirmation.

Examples:

Lock the service API key sample-key of service ID sample-service:

ibmcloud iam service-api-key-lock sample-key sample-service
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:

ibmcloud tg gwd $gateway -f







 Deleting a transit gateway with the API 

To delete a transit gateway with the API, follow these steps:



1. Remove all connections from the transit gateway.
2. Request the deletion of the gateway with the API.





 Request 

To delete a transit gateway, set the following parameters:



Table 1. Path parameters for deleting a transit gateway

 Path parameters Details 

 id <br>Required <br>string The Transit Gateway identifier 





Table 2. Query parameters for deleting a transit gateway

 Query parameters Details 

 version <br>Required <br>string Requests the version of the API as of a date in the format YYYY-MM-DD. Any date up to the current date can be provided. Specify the current date to request the latest version. <br>Possible values: Value must match regular expression ^[0-9]{4}-[0-9]{2}-[0-9]{2}$ 





 Example request 

This example iiilustrates a transit gateway deletion request:

DELETE /transit_gateways/{id}

"{base_url}/transit_gateways/{id}?version={version}"

curl -X DELETE "https://transit.cloud.ibm.com/v1/transit_gateways/testgateway?version=2022-02-10" -H "accept: /"







 Response 

The following status codes will be returned:



Table 3. Status codes when deleting a transit gateway

 Status code Details 

 204 The transit gateway was deleted successfully.
: The subdomain to delete the secret for. To list subdomains, run ibmcloud ks nlb-dns ls --cluster CLUSTER.

-f
: Optional: Force the command to run with no user prompts.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.





 Example nlb-dns secret rm command 

ibmcloud ks nlb-dns secret rm --cluster mycluster --nlb-subdomain mycluster-a1b2cdef345678g9hi012j3kl4567890-0001.us-south.containers.appdomain.cloud







 webhook-create command 

Virtual Private Cloud

Classic infrastructure

Register a webhook.

ibmcloud ks webhook-create --cluster CLUSTER --level LEVEL --type slack --url URL [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--level LEVEL
: Optional: The notification level, such as Normal or Warning. Warning is the default value.

--type slack
: Required: The webhook type. Currently, Slack is supported.

--url URL
: Required: The URL for the webhook.

-q
: Optional: Do not show the message of the day or update reminders.



 Example webhook-create command 

ibmcloud ks webhook-create --cluster my_cluster --level Normal --type slack --url http://github.com/mywebhook







 api-key commands 

View information about the API key for a cluster or reset it to a new key.



 ibmcloud ks api-key info 

Virtual Private Cloud

Classic infrastructure
: The subdomain to delete the secret for. To list subdomains, run ibmcloud ks nlb-dns ls --cluster CLUSTER.

-f
: Optional: Force the command to run with no user prompts.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example nlb-dns secret rm command 

ibmcloud ks nlb-dns secret rm --cluster mycluster --nlb-subdomain mycluster-a1b2cdef345678g9hi012j3kl4567890-0001.us-south.containers.appdomain.cloud









 webhook-create command 

Virtual Private Cloud

Classic infrastructure

Register a webhook.

ibmcloud ks webhook-create --cluster CLUSTER --level LEVEL --type slack --url URL [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--level LEVEL
: Optional: The notification level, such as Normal or Warning. Warning is the default value.

--type slack
: Required: The webhook type. Currently, Slack is supported.

--url URL
: Required: The URL for the webhook.

-q
: Optional: Do not show the message of the day or update reminders.



 Example webhook-create command 

ibmcloud ks webhook-create --cluster my_cluster --level Normal --type slack --url http://github.com/mywebhook







 api-key commands 

View information about the API key for a cluster or reset it to a new key.



 ibmcloud ks api-key info 

Virtual Private Cloud

Classic infrastructure
ibmcloud es topic-delete-records [--name] TOPIC_NAME [--partition-offset PARTITION:OFFSET;PARTITION:OFFSET]* ] [--force]

Prerequisites: None

Command options:

--name value, -n value
: Topic name.

--partition-offset PARTITION:OFFSET, -p PARTITION:OFFSET
: The partition and offset to delete records from in PARTITION:OFFSET format.
: You can specify multiple --partition-offset options or you can specify multiple PARTITION:OFFSET pairs with semicolon delimiters and surrounded with quotations: 'PARTITION1:OFFSET1;PARTITION2:OFFSET2;PARTITION3:OFFSET3'.

--force, -f (optional)
: Delete records without confirmation.





 ibmcloud es topic-partitions-set 

Set the partitions for a topic.

ibmcloud es topic-partitions-set [--name] TOPIC_NAME --partitions PARTITIONS

Prerequisites: None

Command options:

--name value, -n value
: Topic name.

--partitions value, -p value
: Set the number of partitions for the topic.





 ibmcloud es topic-update 

Update the configuration for a topic.

ibmcloud es topic-update [--name] TOPIC_NAME --config KEY[=VALUE]]* [--default]

Prerequisites: None

Command options:

--name value, -n value
: Topic name.

--config KEY[=VALUE], -c KEY[=VALUE]
: Set a configuration option for the topic as a KEY[=VALUE] pair.
: If VALUE is not given, the '--default' flag is to be specified to indicate resetting the configuration value back to the default. Multiple '--config' options can be specified. Each '--config' option can specify a semicolon-delimited list of assignments. The following list shows valid configuration keys:



* cleanup.policy
* retention.ms
* retention.bytes
* segment.bytes
* segment.ms
: The subdomain to delete the secret for. To list subdomains, run ibmcloud oc nlb-dns ls --cluster CLUSTER.

-f
: Optional: Force the command to run with no user prompts.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example nlb-dns secret rm command 

ibmcloud oc nlb-dns secret rm --cluster mycluster --nlb-subdomain mycluster-a1b2cdef345678g9hi012j3kl4567890-0001.us-south.containers.appdomain.cloud









 webhook-create command 

Virtual Private Cloud

Classic infrastructure

Register a webhook.

ibmcloud oc webhook-create --cluster CLUSTER --level LEVEL --type slack --url URL [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--level LEVEL
: Optional: The notification level, such as Normal or Warning. Warning is the default value.

--type slack
: Required: The webhook type. Currently, Slack is supported.

--url URL
: Required: The URL for the webhook.

-q
: Optional: Do not show the message of the day or update reminders.



 Example webhook-create command 

ibmcloud oc webhook-create --cluster my_cluster --level Normal --type slack --url http://github.com/mywebhook







 api-key commands 

View information about the API key for a cluster or reset it to a new key.



 ibmcloud oc api-key info 

Virtual Private Cloud

Classic infrastructure
: Name of the region, for example, us-south or eu-gb. If not specified, the region logged into, or targeted, will be used.

--force
: Will delete the route without providing the user with any additional prompt.

help | --help | -h
: List options available for the command.





 Example 

The following is an example using the ibmcloud atracker route rm --route my_route command.

Are you sure you want to remove the route with the route ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [y/N]> y
OK
Route with route ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx was successfully removed.

The following is an example using the ibmcloud atracker route rm --route my_route --force command.

This example shows a failed command where the specified route could not be found.

FAILED
Something went wrong. Error: No route found with route name - my_route.







 Viewing a route using the CLI 

Use this command to get information about a route for an IBM Cloud Activity Tracker Event Routing region.

ibmcloud atracker route get --route [ <ROUTE_ID> | <ROUTE_NAME> ] [--region <REGION>] [--output JSON]



 Command options 

--route <ROUTE_ID> | <ROUTE_NAME>
: The route ID or name of the route.

--region <REGION> | -r <REGION>
: Name of the region, for example, us-south or eu-gb. If not specified, the region logged into, or targeted, will be used.

--output JSON
: If specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

help | --help | -h
: List options available for the command.





 Example 

The following is an example using the ibmcloud atracker route get --route my_route --output json command.

{
If unspecified, the encryption_key from the most recent snapshot with the same source volume is used. If this snapshot is the first snapshot of the source volume, the encryption_key from the source volume is used.
* --name: New name for the snapshot.
* --clone-zones: Comma-separated zone names that you want the snapshot clones to reside in. Snapshot fast restore is enabled in the cloned zones.
* --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.
* --tags: Tags for this resource.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is snapshot-delete 

Delete one or more snapshots.

ibmcloud is snapshot-delete (SNAPSHOT1 SNAPSHOT2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command examples 



* ibmcloud is snapshot-delete my-snapshot
* ibmcloud is snapshot-delete r134-2fbe71a8-126e-4a05-80ad-dad45df491a5







 Command options 



* SNAPSHOT1: ID or name of the snapshot.
* SNAPSHOT2: ID or name of the snapshot.
* --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 snapshot-update 

Update a snapshot.
* --rip: ID or name of the existing reserved IP.
* --address: The IP address to reserve, which must not already be reserved on the subnet.
* --auto-delete: If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false. (default: true).
* --ip-name: The user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --sg: ID or name of the security group.
* --allow-ip-spoofing: Disables the source and destination checks on this interface. If false, source IP spoofing is not allowed on this interface. One of: false, true.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-network-interface-delete 

Remove one or more network interfaces from a virtual server instance.

ibmcloud is instance-network-interface-delete INSTANCE (NIC1 NIC2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* NIC1: ID or name of the network interface.
* NIC2: ID or name of the network interface.
* --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 instance-network-interface-reserved-ips 

List all reserved IPs that are associated with a network interface.
ibmcloud dev toolchain-delete [toolchainName] [--force,-f]



 toolchain-delete command parameters 

The following parameters can be used with the toolchain-delete command or by updating the app's cli-config.yml file directly.

Command parameters that are entered on the command line take precedence over the cli-config.yml configuration.



 force 



* Parameter that is used to skip the prompt confirmation for deleting a toolchain.
* Usage: ibmcloud dev toolchain-delete [toolchainName] --force







 trace 



* Use this parameter to provide verbose output.
* Usage: ibmcloud dev toolchain-delete [toolchainName] --trace











 toolchain-get 

View the details of a toolchain. If no toolchain name is provided, you can select one from a list.

Uses the targeted resource group in the IBMCLOUD API Key. For more information, see [Set or View the target Account, Region or Resource Group](https://cloud.ibm.com/docs/cli/reference/ibmcloud?topic=cli-ibmcloud_cliibmcloud_target).

ibmcloud dev toolchain-get [toolchainName] [--output JSON]



 toolchain-get command parameters 

The following parameters can be used with the toolchain-get command or by updating the app's cli-config.yml file directly.

Command parameters that are entered on the command line take precedence over the cli-config.yml configuration.



 json 



* Parameter that is used to output the toolchain details in JSON format.
* Usage: ibmcloud dev toolchain-get [toolchainName] --output JSON







 trace 



* Use this parameter to provide verbose output.
* Usage: ibmcloud dev toolchain-get [toolchainName] --trace











 toolchain-open 

View the URL for the toolchain through the toolchain-open command.