vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* The name of the bucket. =======
* Flag: --bucket BUCKET_NAME
* Optional: The REGION where the bucket is present. If this flag is not provided, the program uses the default option that is specified in config.
* Flag: --region REGION
* Optional: Output FORMAT can be only json or text.
* Flag: --output FORMAT









 Delete an object 



* Action: Delete an object from a bucket in a user's IBM Cloud Object Storage account.
* Usage:ibmcloud cos object-delete --bucket BUCKET_NAME --key KEY [--region REGION] [--force] [--output FORMAT]
* Parameters to provide:



* The name of the bucket.



* Flag: --bucket BUCKET_NAME



* The KEY of the object.



* Flag: --key KEY



* Optional: The REGION where the bucket is present. If this flag is not provided, the program uses the default option that is specified in config.



* Flag: --region REGION



* Optional: The operation will do not ask for confirmation.
* Flag: --force
* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT











 Delete multiple objects 



* Action: Delete multiple objects from a bucket in a user's IBM Cloud Object Storage account.
* Usage:ibmcloud cos objects-delete --bucket BUCKET_NAME --delete STRUCTURE [--region REGION] [--output FORMAT]
* Parameters to provide:



* The name of the bucket.



* Flag: --bucket BUCKET_NAME



* A STRUCTURE using either shorthand or JSON syntax.



* Flag: --delete STRUCTURE
* Shorthand Syntax: --delete 'Objects=[{Key=string},{Key=string}],Quiet=boolean'
* JSON Syntax: --delete file://<filename.json> ======= The --delete command takes a JSON structure listing the objects to delete.
A Transport Layer Security (TLS) secret contains a signed TLS certificate, including all its intermediate certificates, and its corresponding private key from a certificate authority (CA). Use TLS secrets when you work with custom domain mappings.

To see CLI help for creating a TLS secret, run ibmcloud ce secret create --format tls.

The following example creates an TLS secret that is named mysecret-tls. The certificate chain that corresponds to the custom domain is contained in the file certificate.txt and the matching private key file is contained in the file privatekey.txt. Both of these files are located in the root directory of the local workstation.

ibmcloud ce secret create --name mysecret-tls --format tls --cert-chain-file certificate.txt --private-key-file privatekey.txt





 Example output for a TLS secret 

Creating TLS secret mysecret-tls...
OK







 ibmcloud ce secret delete 

Delete a secret.

ibmcloud ce secret delete --name SECRET_NAME [--force] [--ignore-not-found] [--quiet]



 Command Options 

--name, -n
: The name of the 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 secret delete --name mysecret-genericfromfile -f





 Example output 

Deleting secret mysecret-genericfromfile...
OK







 ibmcloud ce secret get 

Display the details of a secret.
: UUID of the API key, exclusive with APIKEY_NAME.

SERVICE_ID_NAME (required)
: Name of the service ID, exclusive with SERVICE_ID_UUID.

SERVICE_ID_UUID (required)
: UUID of the service ID, exclusive with SERVICE_ID_NAME.

-f, --force
: Delete without confirmation.





 Examples 

Delete service API key sample-key of service ID sample-service:

ibmcloud iam service-api-key-delete sample-key sample-service







 ibmcloud iam service-api-key-lock 

Lock a service API key:

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



 Command options 

APIKEY_NAME (required)
: Name of the API key, exclusive with APIKEY_UUID.

APIKEY_UUID (required)
: UUID of the API key, exclusive with APIKEY_NAME.

SERVICE_ID_NAME (required)
: Name of the service ID, exclusive with SERVICE_ID_UUID.

SERVICE_ID_UUID (required)
: UUID of the service ID, exclusive with SERVICE_ID_NAME.

-f, --force
: Lock without confirmation.





 Examples 

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

ibmcloud iam service-api-key-lock sample-key sample-service







 ibmcloud iam service-api-key-unlock 

Unlock a service API key:

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



 Command options 

APIKEY_NAME (required)
: Name of the API key, exclusive with APIKEY_UUID.

APIKEY_UUID (required)
: UUID of the API key, exclusive with APIKEY_NAME.

SERVICE_ID_NAME (required)
From the [IBM Cloud console)](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes. The list shows all volumes and the Encryption column displays either "Provider Managed" or the name of the KMS that is used for custoner-managed encryption.
2. Click the name of a volume to see its details.
3. In the Encryption Instance field, click the link of the KMS instance. The KMS instance overview page is displayed.

If you created your KMS instance by using a private endpoint, these instances and associated root keys do not appear in the UI. Use the Key Protect or Hyper Protect Crypto Services CLI or API to verify key rotation instead.
4. Click KMS Keys (Hyper Protect Crypto Services) or Key (Key Protect). The list of all keys in the instance is displayed. The Last updated column shows the date when the key was created or rotated.
5. Click the Actions menu in the row of the key that you want to know more about. Select View key details. A side panel opens and information about the key is displayed. You can see the key name, key ID, CRN, creation date, version date, last updated date, last rotated date, and so on.



After you [rotate the key](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-key-rotation), the version ID field and key version date are updated. The rotated key retains its original name and ID in the list of KMS instances.





 User actions that impact root key states and resource status 

Root keys move to various states as a result of the actions that you take, and different root key states impact resources differently. The following table describes what happens to a resource when you disable, enable, delete, and restore a root key.

Disable root key

Enable root key

Delete root key



Table 1. Disable root key
* kp import-token [nonce-encrypt](https://cloud.ibm.com/docs/key-protect?topic=key-protect-key-protect-cli-referencekp-import-token-nonce-encrypt) : add the -c (--cbc) option; encrypt the nonce using the AES-CBC encryption algorithm; only supported for HPCS







 kp key 



* kp key [delete](https://cloud.ibm.com/docs/key-protect?topic=key-protect-key-protect-cli-referencekp-key-delete) : add the -f (--force) option to delete a key, with force, which is used to delete a key that has existing "registrations"







 kp keys 



* kp [keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-key-protect-cli-referencekp-keys) : add the -n (--number-of-keys) and -s (--starting-offset) options to retrieve a subset of keys











 CLI version 0.4.0 (deprecated) 

Release date: 2020-05-01

Documentation: [CLI reference, version 0.4.0](https://cloud.ibm.com/docs/key-protect?topic=key-protect-cli-reference-040)

Major changes were made to the ibmcloud kp command structure.



 Add these commands 



* kp import-token create: create an import token
* kp import-token key-encrypt: encrypt the key that you want to import to the service
* kp import-token nonce-encrypt: encrypt the nonce that is generated by Key Protect
* kp import-token show: retrieve an import token
* kp key: perform operations on keys
* kp keys: list the keys that are available in your Key Protect instance
* kp region-set: target a different Key Protect regional endpoint







 Deprecate these commands
Service instance my-cos-1 with ID crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:4b636e74-f3ca-40bb-80b8-3bd21801ccb8:: is deleted successfully

 view resources (COS and KMS should no longer exist)
$ ibmcloud resource service-instances

Retrieving instances with type service_instance in resource group Default in all locations under account <account name> as <email address>...
OK
No service instance found.





 Example 3 

This example shows what happens when one of the following occurs between COS and Key Protect (KP) - COS is not able to access the Key Protect root key.



* Delete the KP root key
* Remove the CMS/KP authorization policy



This example does not show command output except when relevant.

 create a Cloud Object Storage (COS) service instance
 "lite" is the pricing plan and "global" is the region
$ COS_NAME=my-cos-1

$ ibmcloud resource service-instance-create $COS_NAME cloud-object-storage lite global

 capture the COS instance id (GUID)
$ COS_INSTANCE_ID=c488e11a-c8a0-4688-b002-9327266ea55f

 create a Key Management Service (KMS) service instance
 "tiered-pricing" is the pricing plan and "us-south" is the region
$ KMS_NAME=my-kms-1

$ ibmcloud resource service-instance-create $KMS_NAME kms tiered-pricing us-south

 capture the Key Protect (KP) instance id (GUID)
$ KP_INSTANCE_ID=26f4b198-952a-47ab-9f44-ef69c038b3c5

 create a policy for COS to read KMS; source is COS, target is KMS (Key Protect)
To delete data that is stored within Code Engine, such as Docker Hub credentials, batch job templates, or an IBM container registry API key, [delete your Code Engine project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-projectdelete-project).

When you delete a project from the console or with the CLI, it is soft deleted and can be restored. You must restore your project within 7 days or it is permanently deleted. For more information about restoring projects, see [Restoring deleted projects](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-projectrestore-softdelete-project). To permanently delete a project, see [Permanently deleting projects](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-projectperm-delete-project).

When you delete a project, any projects that are not permanently deleted count toward the maximum of 20 total projects per region that are allowed.

By using the --force option with the [project delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-delete) command, the delete is forced without confirmation.

ibmcloud ce project delete --name myproject --force

Example output

Deleting project myproject
OK
-n NAME (optional)
: The new name of the API key.

-d DESCRIPTION (optional)
: The new description of the API key.





 Examples 

Update the description of an API key:

ibmcloud iam api-key-update MyKey -d "the new description of my key"

The iam-identity.apikey.manage privilege is required for the account when the NAME and UUID command options are used. For more information, see [Managing user API keys](https://cloud.ibm.com/docs/account?topic=account-userapikey&interface=uimanage-user-keys) and [IAM Identity Service](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsiam-identity-service).







 ibmcloud iam api-key-delete 

Delete a IBM Cloud platform API key:

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



 Command options 

NAME (required)
: Name of the API key to be deleted, exclusive with UUID.

UUID (required)
: UUID of the API key to be deleted, exclusive with NAME.

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







 ibmcloud iam api-key-lock 

Lock a platform API key:

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



 Command options 

NAME (required)
: Name of the API key to be locked, exclusive with UUID.

UUID (required)
: UUID of the API key to be locked, exclusive with NAME.

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





 Examples 

Lock API key test-api-key:

ibmcloud iam api-key-lock test-api-key

Lock API key with given UUID without confirmation:
--service-endpoint SERVICE_ENDPOINT_TYPE
: Type of the service endpoint. Possible values are 'public', 'private'.

-f, --force
: Force creation without confirmation





 Examples 

Create a service binding between service alias my-service-alias and app my-app with role Administrator:

ibmcloud resource service-binding-create my-service-alias my-app Administrator







 ibmcloud resource service-binding-delete 

Delete a service binding.

ibmcloud resource service-binding-delete SERVICE_ALIAS [-f, --force]



 Command options 

SERVICE_ALIAS_NAME (required)
: Service alias name

-f, --force
: Force deletion without confirmation





 Examples 

Delete the service binding between service alias my-service-alias and app my-app:

ibmcloud resource service-binding-delete my-service-alias my-app







 ibmcloud resource service-keys 

List service keys of service instance or service alias.

ibmcloud resource service-keys [ --instance-id ID | --instance-name NAME | --alias-id ID | --alias-name NAME ]



 Command options 

--instance-id
: Service Instance ID

--instance-name
: Service Instance Name

--alias-id
: Service Alias ID

--alias-name
: Service Alias Name





 Examples 

List service keys of service instance my-service-instance:

ibmcloud resource service-keys --instance-name my-service-instance







 ibmcloud resource service-key 

Displays the details of any number of service keys, where the first n characters of the service key name matches the supplied KEY_NAME.

ibmcloud resource service-key (NAME | ID) [-g RESOURCE_GROUP] [--id]



 Command options 

NAME
: Name of the key

ID
: ID of the key

-g
: Resource group name

--id
: Display the ID of service key. This option is exclusive with '--output'.

-g RESOURCE_GROUP
: Resource group name
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. This action is called cryptoshredding.

Cryptoshredding is a destructive action. When the key is deleted, your data is unrecoverable even from a soft delete state.





 Backups Removal 

Backups cannot be manually deleted. However, if you delete your deployment, its backups are deleted automatically.





 Reenabling from a soft delete
ibmcloud iam service-api-key-update (APIKEY_NAME|APIKEY_UUID) (SERVICE_ID_NAME|SERVICE_ID_UUID) [-n, --name NEW_NAME] [-d, --description DESCRIPTION] [-f, --force]



 Command options 

APIKEY_NAME (required)
: Name of the API key, exclusive with APIKEY_UUID.

APIKEY_UUID (required)
: UUID of the API key, exclusive with APIKEY_NAME.

SERVICE_ID_NAME (required)
: Name of the service ID, exclusive with SERVICE_ID_UUID.

SERVICE_ID_UUID (required)
: UUID of the service ID, exclusive with SERVICE_ID_NAME.

-n, --name
: New name of the service API key.

-d, --description
: New description of the service API key.

-f, --force
: Update without confirmation.





 Examples 

Rename service API key sample-key to new-sample-key:

ibmcloud iam service-api-key-update sample-key sample-service -n new-sample-key







 ibmcloud iam service-api-key-delete 

Delete a service API key:

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



 Command options 

APIKEY_NAME (required)
: Name of the API key, exclusive with APIKEY_UUID.

APIKEY_UUID (required)
: UUID of the API key, exclusive with APIKEY_NAME.

SERVICE_ID_NAME (required)
: Name of the service ID, exclusive with SERVICE_ID_UUID.

SERVICE_ID_UUID (required)
: UUID of the service ID, exclusive with SERVICE_ID_NAME.

-f, --force
: Delete without confirmation.





 Examples 

Delete service API key sample-key of service ID sample-service:
"id": "2cbea94c-6070-4a24-b0f8-7a56e4d7cb6f",
"creationDate": "2020-06-15T16:05:53Z"
}
}
] ! ! ! !

 list the bucket
$ ibmcloud cos list-buckets --ibm-service-instance-id $COS_INSTANCE_ID

OK
1 bucket found in your account:
Name Date Created
my-cos-kms-bucket Jun 15, 2020 at 16:07:38

 upload an object to COS
$ ibmcloud cos put-object --bucket $COS_BUCKET --key '/cos-file.txt' --body cos-file-upload.txt

OK
Successfully uploaded object '/cos-file.txt' to bucket 'my-cos-kms-bucket'.

 get the object from COS
$ ibmcloud cos get-object --bucket $COS_BUCKET --key '/cos-file.txt' cos-file-download.txt

OK
Successfully downloaded '/cos-file.txt' from bucket 'my-cos-kms-bucket'
20 B downloaded.

 verify that the upload and download files are the same
$ cat cos-file-upload.txt

This is a test file

$ cat cos-file-download.txt

This is a test file

 delete the object
$ ibmcloud cos delete-object --bucket $COS_BUCKET --key '/cos-file.txt' --force

OK
Delete '/cos-file.txt' from bucket 'my-cos-kms-bucket' ran successfully.

 delete the bucket
$ ibmcloud cos delete-bucket --bucket $COS_BUCKET --force

OK
Successfully deleted bucket 'my-cos-kms-bucket'.
"keyVersion": { "id": "2cbea94c-6070-4a24-b0f8-7a56e4d7cb6f", "creationDate": "2020-06-15T16:05:53Z"
}
}
]

 list the bucket
$ ibmcloud cos list-buckets --ibm-service-instance-id $COS_INSTANCE_ID

OK
1 bucket found in your account:
Name Date Created
my-cos-kms-bucket Jun 15, 2020 at 16:07:38

 upload an object to COS
$ ibmcloud cos put-object --bucket $COS_BUCKET --key '/cos-file.txt' --body cos-file-upload.txt

OK
Successfully uploaded object '/cos-file.txt' to bucket 'my-cos-kms-bucket'.

 get the object from COS
$ ibmcloud cos get-object --bucket $COS_BUCKET --key '/cos-file.txt' cos-file-download.txt

OK
Successfully downloaded '/cos-file.txt' from bucket 'my-cos-kms-bucket'
20 B downloaded.

 verify that the upload and download files are the same
$ cat cos-file-upload.txt

This is a test file

$ cat cos-file-download.txt

This is a test file

 delete the object
$ ibmcloud cos delete-object --bucket $COS_BUCKET --key '/cos-file.txt' --force

OK
Delete '/cos-file.txt' from bucket 'my-cos-kms-bucket' ran successfully.

 delete the bucket
$ ibmcloud cos delete-bucket --bucket $COS_BUCKET --force

OK
Successfully deleted bucket 'my-cos-kms-bucket'.
Why do I fail to see the changes to my key in Azure Key Vault? 

After you use Unified Key Orchestrator to change the state or installation status of a key in Azure Key Vault, you fail to see the changes in the Azure UI.

  What’s happening 

The activated key in Azure Key Vault is not updated after you change the key state or activation status in Unified Key Orchestrator.

  Why it’s happening 

When you make changes to a managed key in Unified Key Orchestrator, it can take up to 2 minutes to reflect the changes in the Azure UI.

  How to fix it 

Wait for 2 minutes and refresh the Azure UI to see the changes.
Why isn't my gateway showing Provisioned status yet? 

After you order a direct link, it can take up to 30 minutes to complete the configuration and show "Provisioned" status.

  What’s happening 

My gateway still shows Pending status.

  Why it’s happening 

It can take up to 30 minutes for provisioning of your direct link to be completed.

  How to fix it 

If the gateway is not showing Provisioned status 30 minutes after ordering, open a [support case](https://cloud.ibm.com/unifiedsupport/cases/form) in the IBM console to further troubleshoot.
a395b603-74bf-4703-8fcb-b68e0b4d6960 pvc-479d590f-ca72-4df2-a30a-0941fceeca42 available 10 3000 5iops-tier data 2019-08-17T12:29:18-05:00 us-south-1 a8a12accd63b437bbd6d58fb6a462ca7
8. Using the volume ID, list the details for your Block Storage for Classic instance to ensure that your Key Protect root key is stored in the storage instance. You can find the root key in the Encryption key field of your CLI output.

ibmcloud is vol <volume_ID>

Example output

ID a395b603-74bf-4703-8fcb-b68e0b4d6960
Name pvc-479d590f-ca72-4df2-a30a-0941fceeca42
Status available
Capacity 10
IOPS 3000
Profile 5iops-tier
Encryption key crn:v1:bluemix:public:kms:us-south:a/6ef045fd2b43266cfe8e6388dd2ec098:53369322-958b-421c-911a-c9ae8d5156d1:key:47a985d1-5f5e-4477-93fc-12ce9bae343f
Encryption user_managed
Resource group a8a12accd63b437bbd6d58fb6a462ca7
Created 2019-08-17T12:29:18-05:00
Zone us-south-1
Volume Attachment Instance Reference







 Customizing the default storage settings 

You can change some default PVC settings by using a customized storage class or a Kubernetes secret to create Block Storage for VPC with your customized settings.

What is the benefit of using a secret and specifying my parameters in a customized storage class?
Why is my Direct Link instance suspended? 

My Direct Link instance has been suspended.

  What’s happening 

The status of my direct link indicates a Suspended status.

  Why it’s happening 

This might be due to an issue with your billing, such as a missed payment.

  How to fix it 

If this is the case, contact IBM Support to assist you in getting your instance up and running.
Table 1.Instance status conflicts

 Status Action Conflict 

 Running start yes 
 Stopped Any action other than start yes 
 Not running pause yes 
 Not running reboot yes 
 Not paused resume yes 
 Paused Any action other than resume yes 







 Why can't I add my SSH key? 

If you try to add an SSH key to your account and get an error that the key can't be parsed, ensure there are no line breaks in the string. An SSH key is a continuous string of characters; sometimes line breaks are introduced when the SSH key is copied from a terminal. To avoid this issue, first paste your SSH key into a text editor and remove any line breaks. Then, copy the SSH key from the text editor and paste it into the VPC UI, CLI, or API.





 How do I reregister a RHEL virtual server instance? 

If you see this error message:

This system is not registered with an entitlement server.

Your REHL virtual server instance was unregistered from the capsule server. To resolve this issue, run the reregister-ng-rhel-vsi.sh script to reregister the virtual server instance.

!/bin/bash

 =============================================================================
 IBM Confidential
 © Copyright IBM Corp. 2020

 The source code for this program is not published or otherwise divested of
 its trade secrets, irrespective of what has been deposited with the
 U.S. Copyright Office.
 =============================================================================