vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud schematics workspace delete --id WORKSPACE_ID [--force]

Command options



Schematics Workspaces delete flags

 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace that you want to remove. To find the ID of your workspace, run ibmcloud schematics workspace list command. 
 --force or -f Optional Force the deletion of your workspace without command-line prompts. 



Example

ibmcloud schematics workspace delete --id myworkspace-a1aa1a1a-a11a-11





 ibmcloud schematics workspace get 

Retrieve the details of an existing workspace, including the values of all input variables.

Syntax

ibmcloud schematics workspace get --id WORKSPACE_ID [--output OUTPUT]

Command options



Schematics Workspaces get flags

 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace, for which you want to retrieve the details. To find the Resource ID of a workspace, run ibmcloud schematics workspace list command to view the of list service instances. From your resource group get an Resource ID for the --id flag. 
 --output or -o Optional Returns the command-line output in JSON format. Currently only JSON file format is supported. 
 --json or -j Deprecated Prints the output in the JSON format. 



Example

ibmcloud schematics workspace get --id myworkspace-a1aa1a1a-a11a-11 --json





 ibmcloud schematics workspace import 

You can import an existing resource with an valid resource address into your Workspace state file. You need to ensure that the resource is only imported once and to a single Workspace. Otherwise, you may see unwanted behavior if the resource is defined in multiple workspaces. Review the [Terraform documentation](https://developer.hashicorp.com/terraform/cli/commands/importusage) for details on how to use the import command.

Syntax
ibmcloud ce revision delete --name REVISION_NAME [--force] [--ignore-not-found] [--quiet]



 Command Options 

--name, -n
: The name of the application revision. 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 revision delete -n newapp-mytest-00004 -f





 Example output 

Deleting application revision 'newapp-mytest-00004'...
OK







 ibmcloud ce revision events 

Display the events of application revision instances.

ibmcloud ce revision events (--instance REVISION_INSTANCE | --revision REVISION_NAME) [--output OUTPUT] [--quiet]



 Command Options 

--instance, -i
: The name of a specific application instance. Use the rev get command to find the instance name. This value is required if --revision is not specified.

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

--revision, --rev, -r, --name, -n
: Display the events of all the instances of the specified application revision. This value is required if --instance is not specified.





 Example
ibmcloud ce subscription cos delete --name COS_SOURCE_NAME [--force] [--ignore-not-found] [--no-wait] [--quiet] [--wait] [--wait-timeout WAIT_TIMEOUT]



 Command Options 

--name, -n
: The name of the IBM Cloud Object Storage event subscription. 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.

--no-wait, --nw
: Delete the IBM Cloud Object Storage event subscription and do not wait for the subscription to be deleted. If you specify the --no-wait option, the subscription delete begins and does not wait. Use the subscription cos get command to check the subscription status. 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.

--wait, -w
: Delete the IBM Cloud Object Storage event subscription and wait for the subscription to be deleted. If you specify the --wait option, the subscription delete waits for a maximum time in seconds, as set by the --wait-timeout option, for the subscription to be deleted. This command exits when the subscription is deleted or whenever --wait-timeout is reached, whichever comes first. This value is optional. The default value is true.

--wait-timeout, --wto
: The length of time in seconds to wait for the IBM Cloud Object Storage event subscription to be deleted. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 15.





 Example 

ibmcloud ce subscription cos delete --name mycosevent -f





 Example output
--ingestion-key LOGDNA_INGESTION_KEY
: LOGDNA_INGESTION_KEY is the ingestion key for the IBM Cloud Activity Tracker Event Routing instance.

--output FORMAT
: Currently support format is 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 target update --name eu-de-logdna-target --target-crn "crn:v1:bluemix:public:logdna:eu-de:a/11111111111111111111111111111111:22222222-2222-2222-2222-222222222222::" --ingestion-key xxxxxx command.

This example shows an example successful target update.

OK
Target
Name: eu-de-logdna-target
ID: cccccccc-cccc-cccc-cccc-cccccccccccc
CRN: crn:v1:bluemix:public:atracker:eu-de:a/11111111111111111111111111111111::target:cccccccc-cccc-cccc-cccc-cccccccccccc
Type: logdna
LogDNA Target CRN: crn:v1:bluemix:public:logdna:eu-de:a/11111111111111111111111111111111:22222222-2222-2222-2222-222222222222::
CreatedAt: 2022-05-06T18:59:26.760Z
UpdatedAt: 2022-05-06T19:16:50.090Z







 Deleting a target using the CLI 

Use this command to delete a target.

ibmcloud atracker target rm --target TARGET [--force]



 Command options 

--target TARGET
To delete a route by using the CLI, run the following command:

ibmcloud is vpc-routing-table-route-delete VPC ROUTING_TABLE ROUTE [-f, --force]

Where:



* VPC is the ID of the VPC.
* ROUTING_TABLE is the ID of the VPC routing table.
* ROUTE is the ID of the VPC route.
* -f, --force forces the operation without confirmation.







 Deleting a route with the API 

To delete a route with 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:

export VpcId=<your_vpc_id>
export RoutingTableId=<your_routing_table_id>
export RouteId=<your_route_id>
3. Delete a route:



curl -X GET "$vpc_api_endpoint/v1/vpcs/$VpcId/routing_tables/$RoutingTableId/routes/$RouteId?version=$api_version&generation=2" -H "Authorization: $iam_token"
capture the name of the COS bucket that was created
$ COS_BUCKET=my-cos-kms-bucket

 view the KP registration; it's a result of creating the COS bucket
$ ibmcloud kp registrations --output json

[
{
"keyId": "52a9d772-8982-4620-bfb4-b070dd812a0c",
"resourceCrn": "crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:9d4353d8-6b85-4689-90dd-1ccfb4a275ab:bucket:my-cos-kms-bucket",
"createdBy": "crn-crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:9d4353d8-6b85-4689-90dd-1ccfb4a275ab::",
"creationDate": "2020-06-15T20:41:23Z",
"lastUpdated": "2020-06-15T20:41:23Z",
"keyVersion": {
"id": "52a9d772-8982-4620-bfb4-b070dd812a0c",
"creationDate": "2020-06-15T20:36:46Z"
}
}
]

 delete the authorization policy between COS AND KMS - this breaks everything
$ ibmcloud iam authorization-policy-delete $COS_KMS_AUTHORIZATION --force

 delete the KP root key - this fails because the registration was not deleted
$ ibmcloud kp key delete $MY_COS_KEY_ID
capture the name of the COS bucket that was created
$ COS_BUCKET=my-cos-kms-bucket

 view the KP registration; it's a result of creating the COS bucket
$ ibmcloud kp registrations --output json

[
{
"keyId": "52a9d772-8982-4620-bfb4-b070dd812a0c",
"resourceCrn": "crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:9d4353d8-6b85-4689-90dd-1ccfb4a275ab:bucket:my-cos-kms-bucket",
"createdBy": "crn-crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:9d4353d8-6b85-4689-90dd-1ccfb4a275ab::",
"creationDate": "2020-06-15T20:41:23Z",
"lastUpdated": "2020-06-15T20:41:23Z",
"keyVersion": { "id": "52a9d772-8982-4620-bfb4-b070dd812a0c", "creationDate": "2020-06-15T20:36:46Z"
}
}
]

 delete the authorization policy between COS AND KMS - this breaks everything
$ ibmcloud iam authorization-policy-delete $COS_KMS_AUTHORIZATION --force

 delete the KP root key - this fails because the registration was not deleted
$ ibmcloud kp key delete $MY_COS_KEY_ID
Similarly, added support for verifying that the --registry-secret and the --git-repo-secret exist unless the --force option is specified for the build create and build update commands. The --force option specifies to avoid verification of the existence of the registry secret and the Git repo secret (as applicable).<br> * Updated the output of the project list and project get commands to display whether a project is enabled or disabled. If the status of your IBM Cloud account is disabled, then the status of any Code Engine projects in that account are disabled.<br> * Updated the output of the project current command.<br> * Fixed various bugs.<br><br><br> 
 1.10.0 23 June 2021 <br><br> * Updated list commands to display a warning when the quota is reached for that resource. For example, the app list command displays a warning when the application quota is reached.<br> * Added the project tag command. Use this command to add and remove tags for a single project.<br> * Updated the revision get command to display information for events and instances.<br> * Updated the jobrun list and jobrun delete commands to filter by --job. You can use the --job filter to list or delete job runs that reference a specified job configuration.<br> * Updated the buildrun list and buildrun delete commands to filter by --build. You can use the --build filter to list or delete build runs that reference a specified build configuration.<br><br><br> 
 1.9.0 15 June 2021 <br><br> * Added support for the --instances option with the job create, job update, jobrun submit, and jobrun resubmit commands. Use this option to specify the number of instances for the job or job run.<br> * Added the --ignore-not-found option on all Code Engine delete commands, except for the project delete command. This option specifies that if the resource is not found, do not fail the delete.<br> * Updated the behavior of the app create, app update, job create, job update, jobrun submit, jobrun resubmit commands to fail if a referenced configmap or secret does not exist.
ibmcloud tg gateway-delete|gwd GATEWAY_ID [-f, --force] [-h, --help]



 Command options 

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 

Delete gateway with no confirmation.

ibmcloud tg gwd $gateway -f

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









 Connections 

This section provides information about CLI commands for connections functionality.



 ibmcloud tg connections 

List connections on the given transit gateway.

ibmcloud tg connections|cs GATEWAY_ID [--output json] [-h, --help]



 Command options 

GATEWAY_ID
: ID of the gateway you want connections for.

--output json
: Optional: Specify if you want the output displayed in JSON format.

--help | -h
: Optional: Get help on this command.





 Example 

List the connections on the gateway.

ibmcloud tg cs $gateway

Other commands will require a connection ID, save the ID as an environment variable so you can use it later, for example:

connection="4892849f-368e-9999-bb58-8888fb21e513"

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







 ibmcloud tg connection 

Retrieve details about a specific connection.

ibmcloud tg connection|c GATEWAY_ID CONNECTION_ID [--output json] [-h, --help]



 Command options 

GATEWAY_ID
: ID of the gateway the connection is on.

CONNECTION_ID
: ID of the connection you want details for.

--output json
: Optional: Specify if you want the output displayed in JSON format.

--help | -h
: Optional: Get help on this command.





 Example 

Request details for a specific connection ID.
: Delete the project reclamation and do not wait for the project reclamation to be deleted. If you specify the no-wait option, the project reclamation delete begins and does not wait. Use the reclamation get command to check the project reclamation status. 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.

--wait, -w
: Delete the project reclamation and wait for the project reclamation to be deleted. If you specify the --wait option, the project reclamation delete waits for a maximum time in seconds, as set by the --wait-timeout option, for the project reclamation to be deleted. If the project reclamation is not deleted within the specified --wait-timeout period, the project reclamation delete fails. This value is optional. The default value is true.

--wait-timeout, --wto
: The length of time in seconds to wait for the project reclamation to be deleted. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 600.





 Example 

This example permanently deletes the myproject project that is in soft deleted status. By using the --force option with this command, the delete is forced without confirmation. You can use the [reclamation list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation-list) command to display a list of all projects that are in soft deleted status.

ibmcloud ce reclamation delete --name myproject --f





 Example output 

Hard deleting project 'myproject'...
OK







 ibmcloud ce reclamation get 

Display the details of a single project reclamation.

ibmcloud ce reclamation get (--name PROJECT_NAME | --id PROJECT_ID) [--output OUTPUT] [--quiet]



 Command Options 

--id, --guid
: The ID of the project.
The following is an example using the ibmcloud atracker target rm --target xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -force command.This example shows a failed command where the specified target could not be found. Are you sure you want to remove the Target bearing Target ID 33333333-3333-3333-3333-333333333333? y/N] ! ! ! > y
FAILED
Something went wrong. Error:
Status Code: 404
Incident ID: 67a33257-d5a4-46ec-94d9-14eb70e94f3d
Code: not_found
Message: The target id specified in target_id field is not found.
<-- </section "id="section-target-rm-example-cos" "> --><-- </section "class="ph" id="section-target-delete-cli-cos" "> --><-- <section "class="ph" id="section-target-validate-cli-cos" "> --> Validating a target using the CLI Use this command to validate that a target is correctly configured for an IBM Cloud Activity Tracker Event Routing region. ibmcloud atracker target validate --target TARGET --region REGION] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-target-validate-options-cos" "> --> Command options --target TARGET: The ID or name of the target.--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 FORMAT: Currently supported format is JSON. If specified, output will be returned in JSON format.
Alternatively, you can use the [project restore](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-restore) command to restore a soft deleted project to an active state.







 Permanently deleting projects 



 Permanently deleting projects from the console 

After you soft delete a project (or delete the project with reclamation), you can restore it or permanently delete it from the console. When a project is permanently deleted, it cannot be restored.



1. From the [Projects page on the Code Engine console](https://cloud.ibm.com/codeengine/projects), view the list of projects in your region. The number of project reclamations is displayed.
2. Click the link for project reclamations.
3. From the Project reclamations page, you can view the number of remaining days that you can restore your project. To permanently delete your project, click Delete.



If you take no action on deleted projects that are listed on the Project reclamations page, the project is automatically deleted permanently after 7 days.





 Permanently deleting projects with the CLI 

If your project is soft deleted, you can use the [reclamation delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation-delete) command to permanently delete the project. By using the --force option with this command, the delete is forced without confirmation.

ibmcloud ce reclamation delete -n myproject --f

Example output

Hard deleting project 'myproject'...
OK

If your project is not soft deleted, then to permanently delete a project so that it cannot be restored, use the --hard option with the [project delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-delete) command to specify to immediately and permanently delete the project. For example, to permanently delete the myproject3 project,

ibmcloud ce project delete --name myproject3 --hard

Example output
ibmcloud ce domainmapping create --domain-name DOMAIN_NAME [--target-type app] --tls-secret <tls-secret-name> [--quiet]



 Command Options 

--domain-name, --dn, -n, --name
: Specify the name of the domain mapping. This name must be a valid fully qualified domain name (FQDN). For example, www.example.com. This value is required.

--target, -t
: The name of the target application. This value is required.

--tls-secret, --secret, --tls
: Specify a TLS secret that contains the certificate including all its intermediate certificates and the corresponding private key for the domain mapping. The certificate must be signed by a trusted, public certificate authority (CA). Self-signed certificates are not supported. This value is required.

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





 Example 

The following example creates a custom domain mapping between the Code Engine myapp application and the custom domain, www.example.com and uses the TLS secret, mytlssecret.

ibmcloud ce domainmapping create --domain-name www.example.com --target myapp --tls-secret mytlssecret





 Example output 

OK
Domain mapping successfully created.







 ibmcloud ce domainmapping delete 

Delete a custom domain mapping.

ibmcloud ce domainmapping delete --domain-name DOMAIN_NAME [--force] [--ignore-not-found] [--quiet]



 Command Options 

--domain-name, --dn, -n, --name
: The name of the domain mapping. 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.
<-- </section "id="section-kp-region-set-example-3" "> --><-- </section "id="section-kp-region-set-examples" "> --><-- <section "id="section-kp-region-set-required" "> --> Required parameters -i, --instance-id: The IBM Cloud instance ID that identifies your Key Protect instance.
You can set an environment variable instead of specifying -i with the following command.

$ export KP_INSTANCE_ID=INSTANCE_ID
<-- </section "id="section-kp-region-set-required" "> --><-- <section "id="section-kp-region-set-optional" "> --> Optional parameters REGION: Specify a regional endpoint. This parameter is optional and if not specified, you are prompted to select a regional endpoint from a list.<-- </section "id="section-kp-region-set-optional" "> --><-- </section "id="section-kp-region-set" "> --><-- <section "id="section-kp-registrations" "> --> kp registrations Registrations are associations between root keys and other cloud resources, such as Cloud Object Storage (COS) buckets or Cloud Databases deployments.For example, in Key Protect you create a root key, which is used by COS to protect data at rest.The relationship between other cloud resources and Key Protect is called a registration.Do not delete a root key if there are resources, such as COS buckets and objects, that rely on the root key. Deleting the root key means you cannot recover those resources. This is known as "crypto shredding" and there is no recovery from this action. ibmcloud kp registrations
-i, --instance-id INSTANCE_ID
-c, --crn-query CRN_PATTERN]
-k, --key-id KEY_ID]
-o, --output OUTPUT] !
Key Management Interoperability Protocol (KMIP) is a communication protocol for the storage and maintenance of key, certificate, and secret objects. The standard is governed by the Organization for the Advancement of Structured Information Standards (OASIS). Hyper Protect Crypto Services provides a dedicated single-tenant KMIP adapter so that VMware vCenter server instances can use Hyper Protect Crypto Services as the Key Management Service (KMS) for VMware vSphere encryption and vSAN encryption.

Hyper Protect Crypto Services



* 2 hours
* 2023-07-04



[Creating and importing encryption keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-tutorial-import-keys)Creating and importing encryption keys

Learn how to create, encrypt, and bring your encryption keys to the cloud by using Hyper Protect Crypto Services.

Hyper Protect Crypto Services



* 30 minutes
* 2023-06-27



[Using Hyper Protect Crypto Services PKCS #11 for Oracle Transparent Database Encryption](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-tutorial-tde-pkcs11)Using Hyper Protect Crypto Services PKCS #11 for Oracle Transparent Database Encryption

Transparent Data Encryption (TDE) is a well-established technology to encrypt sensitive data in databases. TDE is supported by various popular database systems, both in the cloud and on premises, like Oracle® database. With TDE, a database system encrypts data on database storage media, such as table spaces and files, and on backup media. The database system automatically and transparently encrypts and decrypts data when it is used by authorized users and applications. Database users do not need to be aware of TDE and database applications do not need to be adapted specifically for TDE.

Hyper Protect Crypto Services



* 2 hours
* 2023-02-08