vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If this flag is not provided, the program will use the default option specified in config.



* Flag: --region REGION



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT



* Optional: The location where to save the content of the object. If this parameter is not provided, the program uses the default location.



* Parameter: OUTFILE













 Find a bucket 



* Action: Determine the region and class of a bucket in an IBM Cloud Object Storage instance.
* Usage:ibmcloud cos bucket-location-get --bucket BUCKET_NAME [--output FORMAT]
* Parameters to provide:



* The name of the bucket.



* Flag: --bucket BUCKET_NAME



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT











 Get a bucket's class 



* Action: Determine the class of a bucket in an IBM Cloud Object Storage instance.
* Usage:ibmcloud cos bucket-class-get --bucket BUCKET_NAME [--output FORMAT]
* Parameters to provide:



* The name of the bucket.



* Flag: --bucket BUCKET_NAME



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT











 Get bucket CORS 



* Action: Returns the CORS configuration for the bucket in a user's IBM Cloud Object Storage account.
* Usage:ibmcloud cos bucket-cors-get --bucket BUCKET_NAME [--region REGION] [--output FORMAT]
* Parameters to provide:



* 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









 Complete a multipart upload
For more information, see [Controlling access to resources by using tags](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorial).



5. From the Attach the flow log connector to menu, choose a target type for the flow log. Depending on your selection, additional fields might be required.



* Virtual private cloud - Select a VPC. All network traffic within the selected VPC is logged.
* Subnet - Select a VPC and a subnet within the selected VPC. All traffic within the selected subnet is logged.
* Instance - Select a VPC and a virtual server instance that exists within the selected VPC. All traffic for the virtual server instance is logged.
* Interface - Select a VPC, a virtual server instance within the selected VPC, and a specific network interface for the selected virtual server instance. All traffic for the selected network interface is logged.



6. Specify where the logs are written. Flow logs are written to an Object Storage bucket, which must be created as a single-region bucket in the same region as the target resource.



* Cloud Object Storage instances - The Object Storage instance that the wanted bucket resides in.
* Location - This input is unavailable because it is directly tied to the region the target resource resides in.
* Bucket - The wanted IBM Cloud® Object Storage bucket that the flow log collector service writes to.









 Creating a flow log collector from 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 create a flow log collector by using the CLI, run the following command:

ibmcloud is flow-log-create --bucket STORAGE_BUCKET_NAME --target TARGET_ID [--name NAME] --active ACTIVE [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--json]

Where:



* --bucket is the name of the Object Storage bucket.
* --target is the target for the flow log.
For more information about using the JSON editor, see [Context variables in the JSON editor](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-runtime-contextdialog-runtime-context-var-json).

![Shows how to access the JSON editor associated with a slot condition.](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/contextvar-json-slot-condition.png)











 Context variables in the JSON editor 

You can also define a context variable in the JSON editor. You might want to use the JSON editor if you are defining a complex context variable and want to be able to see the full SpEL expression as you add or change it.

The name and value pair must meet these requirements:



* The name can contain any uppercase and lowercase alphabetic characters, numeric characters (0-9), and underscores.

You can include other characters, such as periods and hyphens, in the name. However, if you do, then you must specify the shorthand syntax $(variable-name) every time you subsequently reference the variable. See [Expressions for accessing objects](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-expression-languageexpression-language-shorthand-syntax) for more details.
* The value can be any supported JSON type, such as a simple string variable, a number, a JSON array, or a JSON object.



The following JSON sample defines values for the $dessert string, $toppings_array array, $age number, and $full_name object context variables:

{
"context": {
"dessert": "cake",
"toppings_array": [
"onions",
"olives"
],
"age": 18,
"full_name": {
"first": "Jane",
This value is ignore if service_to_service_enabled is true.

SERVICE_TO_SERVICE indicates if service-to-service authorization]service_-to_-service authorization] ! ! ! ! has been enabled for the bucket. Specify true if service-to-service authorization is enabled and false if service-to-service authorization is not enable. By default, service-to-service authorization is false.
<-- </ul> -->For example, you can use the following cURL request to create a target in Dallas: curl -X PUT https://private.us-south.atracker.cloud.ibm.com/api/v2/targets -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json" -d '{
"name": "My COS target",
"target_type": "cloud_object_storage",
"cos_endpoint": {
"endpoint": "s3.private.us-south.cloud-object-storage.appdomain.cloud",
"target_crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/<account-id>:<instance-id>::",
"bucket": "my-activity-tracking-bucket",
"service_to_service_enabled": true
}
}'
<-- </section "class="ph" id="section-target-update-api-cos" "> --><-- <section "class="ph" id="section-target-delete-api-cos" "> --> Deleting a target using the API You can use the following cURL command to delete a target: curl -X DELETE <ENDPOINT>/api/v2/targets/<TARGET_ID> -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"
Where<-- <ul> --> * <ENDPOINT> is the API endpoint in the region where you plan to configure or manage a target.
The following JSON output represents a registration between a key and a cloud resource.

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.registration+json",
"collectionTotal": 1
},
"resources": [
{
"keyId": "02fd6835-6001-4482-a892-13bd2085f75d",
"resourceCrn": "crn:v1:bluemix:public:<service-name>:<region>:a/<account-id>:<service-instance>:bucket:<bucket-name>",
"createdBy": "IBMid-25555555",
"creationDate": "2010-01-12T05:23:19+0000",
"updatedBy": "IBMid-25555555",
"lastUpdated": "2010-01-12T05:23:19+0000",
"description": "A description of the registration",
"preventKeyDeletion": true,
"keyVersion": {
"id": "02fd6835-6001-4482-a892-13bd2085f75d",
"creationDate": "2010-01-12T05:23:19+0000"
}
}
]
}

The following table describes the properties of a registration.



Table 2. Properties that are associated with a registration.

 Parameter Description 

 keyID The ID that identifies the root key that is associated with the cloud resource. 
 resourceCrn The Cloud Resource Name (CRN) that represents the cloud resource, such as a Cloud Object Storage bucket, that is associated with the key. 
 createdBy The unique identifier for the resource that created the registration. 
 creationDate The date the registration was created. 
 lastUpdated The date the registration was updated. 
 description A description for the registration.
<-- <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. If JSON is not specified, output will be returned in a tabular format.help | --help | -h: List options available for the command.<-- </section "id="section-target-validate-options-cos" "> --><-- <section "id="section-target-validate-example-cos" "> --> Example The following is an example using the ibmcloud atracker target validate --target new-target-name command.This example shows a successfully validated COS target. Target
Name: 		new-target-name
ID: 		xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
CRN: 		crn:v1:staging:public:atracker:us-south:a/xxxxxxxxxx:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
Type: 		cloud_object_storage
COS Endpoint: 		s3.us-west.cloud-object-storage.appdomain.cloud
COS Target CRN: 		crn:v1:staging:public:cloud-object-storage:global:a/xxxxxxxxxx:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx:
COS Bucket: 		cloud-object-my-target
Service to Service Enabled:	true
Write Status: 		success
Created: 		2021-07-21T16:04:15.174Z
Updated: 		2021-07-21T17:49:56.452Z
This can be set by using the [ibmcloud cos config crn](https://cloud.ibm.com/docs/cloud-object-storage-cli-plugin?topic=cloud-object-storage-cli-plugin-ic-cos-cliic-config) command.



* Parameters to provide:



* No parameters to provide.
* Optional: Sets the IBM Service Instance ID in the request.



* Flag: --ibm-service-instance-id



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT









 Extended Bucket Listing 



* Action: Print a list of all the buckets in a user's IBM Cloud Object Storage account. Buckets might be located in different regions.
* Usage:ibmcloud cos buckets-extended [--ibm-service-instance-id ID] [--marker KEY] [--prefix PREFIX] [--page-size SIZE] [--max-items NUMBER] [--output FORMAT]



* Note that you must provide a CRN if you are using IAM authentication. This can be set by using the [ibmcloud cos config crn](https://cloud.ibm.com/docs/cloud-object-storage-cli-plugin?topic=cloud-object-storage-cli-plugin-ic-cos-cliic-config) command.



* Parameters to provide:



* No parameters to provide.
* Optional: Sets the IBM Service Instance ID in the request.



* Flag: --ibm-service-instance-id



* Optional: Specifies the KEY to start with when listing objects in a bucket.



* Flag: --marker KEY



* Optional: Limits the response to keys that begin with the specified PREFIX.



* Flag: --prefix PREFIX



* Optional: The SIZE of each page to get in the service call. This does not affect the number of items returned in the command's output. Setting a smaller page size results in more calls to the service, retrieving fewer items in each call. This can help prevent the service calls from timing out.
Delete an existing bucket 



* Action: Delete an existing bucket in an IBM Cloud Object Storage instance.
* Usage:ibmcloud cos bucket-delete --bucket BUCKET_NAME [--region REGION] [--force] [--output FORMAT]
* Parameters to provide:



* 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: The operation will do not ask for confirmation.



* Flag: --force



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT











 Delete bucket CORS 



* Action: Delete CORS configuration on a bucket in a user's IBM Cloud Object Storage account.
* Usage:ibmcloud cos bucket-cors-delete --bucket BUCKET_NAME [--region REGION] [--output FORMAT]
* Parameters to provide:



* 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 a static website configuration 



* Action: Removes a bucket's static website configuration.
* Usage:ibmcloud cos bucket-website-delete --bucket BUCKET_NAME [--region REGION] [--output FORMAT]
* Parameters to provide:



* 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
: The name or CRN of the source DBaaS service instance. To find the resource name or CRN, use the IBM Cloud command ibmcloud resource service-instances --long.

--output value
: Use the --output option with value json to format output in JSON.







 ibmcloud dbaas backup configure 

This command changes the configuration of backup to IBM Cloud Object Storage for a database cluster.

ibmcloud dbaas backup configure RESOURCE_NAME [--cos-hmac-credentials-path CREDENTIALS_PATH --cos-endpoint COS_ENDPOINT --cos-bucket-crn BUCKET_CRN] [--cos-frequency FREQUENCY] [--output json]



 Command options 

RESOURCE_NAME
: The name or CRN of the source DBaaS service instance. To find the resource name or CRN, use the IBM Cloud command ibmcloud resource service-instances --long.

--cos-hmac-credentials-path value
: Path to the file that contains the HMAC credentials (access_key_id and secret_access_key) in JSON format. You can find the credentials by selecting Service credentials in the IBM Cloud Object Storage web UI. Create a file that contains the complete JSON copied from there or at least what's in the following example. You can also [set HMAC credentials as environment variables](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-mainuhc-setting-hmac-credentials) and omit this command option.

An example of HMAC credentials:

{
"cos_hmac_keys": {
"access_key_id": "abc",
"secret_access_key": "xyz"
}
}

--cos-endpoint value
: Endpoint of IBM Cloud Object Storage. This parameter is required if --cos-bucket-crn is set. In the IBM Cloud Object Storage web UI, select your bucket and you can find Endpoints in the Configuration tab.
--name <TARGET_NAME>
: The name to be given to the target.

Do not include any personal identifying information (PII) in any resource names.

--file <@COS_ENDPOINT_DEFINITION_JSON_FILE>
: A file containing an endpoint definition in the following format:

{
"endpoint": "aaaaa",
"target_crn": "yyyyy",
"bucket": "zzzzzz",
"api_key": "xxxxxx"
}

--endpoint <COS_ENDPOINT>
: The IBM Cloud Object Storage endpoint to be associated with the IBM Cloud Object Storage bucket.

--bucket <COS_BUCKET>
: The name of the IBM Cloud Object Storage bucket to be associated with the target.

--target-crn <COS_TARGET_CRN>
: The CRN of the IBM Cloud Object Storage instance.

--api-key <COS_API_KEY> | <@COS_API_KEY_FILE>
: Your [API key](https://cloud.ibm.com/docs/account?topic=account-manapikey) value or a reference to the API Key file used when logging in. For example, ibmcloud login --apikey $KEYFILE

--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 target update --target my-target --name new-target-name command.

Target
Name: new-target-name
ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
CRN: crn:v1:staging:public:atracker:us-south:a/xxxxxxxxxx:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
ibmcloud atracker target create --name <TARGET_NAME> --type <TARGET_TYPE> ( --file <COS_ENDPOINT_DEFINITION_JSON_FILE> | --endpoint <COS_ENDPOINT> --bucket <COS_BUCKET> --target-crn <COS_TARGET_CRN> --api-key ( <COS_API_KEY> | <@COS_API_KEY_FILE> ) ) [--region <REGION>] [--output JSON]



 Command options 

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

--name <TARGET_NAME>
: The name to be given to the target.

Do not include any personal identifying information (PII) in any resource names.

--type <TARGET_TYPE>
: Only supported value for <TARGET_TYPE> is cloud-object-storage.

--file <@COS_ENDPOINT_DEFINITION_JSON_FILE>
: A file containing an endpoint definition in the following format:

{
"endpoint": "aaaaa",
"target_crn": "yyyyy",
"bucket": "zzzzzz",
"api_key": "xxxxxx"
}

--endpoint <COS_ENDPOINT>
: The IBM Cloud Object Storage endpoint to be associated with the IBM Cloud Object Storage bucket.

--bucket <BUCKET>
: The name of the IBM Cloud Object Storage bucket to be associated with the target.

--target-crn <COS_TARGET_CRN>
: The CRN of the IBM Cloud Object Storage instance.

--api-key <COS_API_KEY> | <@COS_API_KEY_FILE>
: Your [API key](https://cloud.ibm.com/docs/account?topic=account-manapikey) value or a reference to the API Key file used when logging in.
Get a list of storage classes that are created by the ibmcloud-object-storage-plugin.

oc get StorageClass --all-namespaces -l app=ibmcloud-object-storage-plugin -o jsonpath='{range .items[]}{.metadata.name}{"n"}{end}'
4. Get a list of cluster role bindings that are created by the ibmcloud-object-storage-plugin.

oc get ClusterRoleBinding --all-namespaces -l app=ibmcloud-object-storage-plugin -o jsonpath='{range .items[]}{.metadata.name}{"n"}{end}'
5. Get a list of role bindings that are created by the ibmcloud-object-storage-driver.

oc get RoleBinding --all-namespaces -l app=ibmcloud-object-storage-driver -o jsonpath='{range .items[]}{.metadata.namespace}{"t"}{.metadata.name}{"n"}{end}'
6. Get a list of role bindings that are created by the ibmcloud-object-storage-plugin.

oc get RoleBinding --all-namespaces -l app=ibmcloud-object-storage-plugin -o jsonpath='{range .items[]}{.metadata.namespace}{"t"}{.metadata.name}{"n"}{end}'
7. Get a list of cluster roles that are created by the ibmcloud-object-storage-plugin.

oc get ClusterRole --all-namespaces -l app=ibmcloud-object-storage-plugin -o jsonpath='{range .items[]}{.metadata.name}{"n"}{end}'
8. Get a list of deployments that are created by the ibmcloud-object-storage-plugin.
"year": 2003
}

You can make both the $and operator and the equality operator explicit.

See the following example that uses explicit $and and $eq operators:

{
"$and": [
{
"director": {
"$eq": "Lars von Trier"
}
},
{
"year": {
"$eq": 2003
}
}
]
}





 Explicit operators 

All operators, apart from the $eq (equality) and $and (and) operators, must be stated explicitly.





 Combination operators 

Combination operators are used to combine selectors. Three combination operators ($all, $allMatch, and $elemMatch) help you work with JSON arrays, in addition to the common Boolean operators found in most programming languages.

A combination operator takes a single argument. The argument is either another selector, or an array of selectors.



Table 1. Combination operators

 Operator Argument Purpose 

 [$all](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-operatorsthe-all-operator) Array Matches an array value if it contains all the elements of the argument array. 
 [$allMatch](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-operatorsthe-allmatch-operator) Selector Matches and returns all documents that contain an array field, where all the elements match all the specified query criteria. 
 [$and](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-operatorsthe-and-operator) Array Matches if all the selectors in the array match. 
 [$elemMatch](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-operatorsthe-elemmatch-operator) Selector Matches and returns all documents that contain an array field with at least one element that matches all the specified query criteria.
Get a list of cluster roles that are created by the ibmcloud-object-storage-plugin.

oc get ClusterRole --all-namespaces -l app=ibmcloud-object-storage-plugin -o jsonpath='{range .items[]}{.metadata.name}{"n"}{end}'
8. Get a list of deployments that are created by the ibmcloud-object-storage-plugin.

oc get deployments --all-namespaces -l app=ibmcloud-object-storage-plugin -o jsonpath='{range .items[]}{.metadata.namespace}{"t"}{.metadata.name}{"n"}{end}'
9. Get a list of the daemon sets that are created by the ibmcloud-object-storage-driver.

oc get DaemonSets --all-namespaces -l app=ibmcloud-object-storage-driver -o jsonpath='{range .items[]}{.metadata.namespace}{"t"}{.metadata.name}{"n"}{end}'
10. Get a list of the service accounts that are created by the ibmcloud-object-storage-driver.

oc get ServiceAccount --all-namespaces -l app=ibmcloud-object-storage-driver -o jsonpath='{range .items[]}{.metadata.namespace}{"t"}{.metadata.name}{"n"}{end}'
11. Get a list of the service accounts that are created by the ibmcloud-object-storage-plugin.

oc get ServiceAccount --all-namespaces -l app=ibmcloud-object-storage-plugin -o jsonpath='{range .items[]}{.metadata.namespace}{"t"}{.metadata.name}{"n"}{end}'
12. Delete the conflicting resources.
13.
The configuration information is stored in a JSON file that is at /.mc/config.json

mc config host add cos https://s3.us-south.cloud-object-storage.appdomain.cloud xx1111cfbe094710x4819759x57e9999 9f99fc08347d1a6xxxxx0b7e0a9ee7b0c9999c2c08ed0000





 Sample Commands 

A complete list of commands and optional flags and parameters are documented in the [Minio Client Complete Guide](https://docs.min.io/docs/minio-client-complete-guide)



 mb - Make a Bucket 

mc mb cos/my_test_bucket





 ls - List Buckets 

Though all your available buckets are listed, not all objects might be accessible depending on the specified [endpoint's](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints) region.

mc ls cos

[2018-06-05 09:55:08 HST] 0B testbucket1/
[2018-05-24 04:17:34 HST] 0B testbucket_south/
[2018-10-15 16:14:28 HST] 0B my_test_bucket/





 ls - List Objects 

mc ls cos/testbucket1

[2018-11-12 08:09:53 HST] 34B mynewfile1.txt
[2018-05-31 01:49:26 HST] 34B mynewfile12.txt
[2018-08-10 09:49:08 HST] 20MiB newbigfile.pdf
[2018-11-29 09:53:15 HST] 31B testsave.txt





 find - Search for Objects by Name 

A full list of search options is available in the [complete guide](https://docs.min.io/docs/minio-client-complete-guidefind)
Get a list of the service accounts that are created by the ibmcloud-object-storage-plugin.

kubectl get ServiceAccount --all-namespaces -l app=ibmcloud-object-storage-plugin -o jsonpath='{range .items[]}{.metadata.namespace}{"t"}{.metadata.name}{"n"}{end}'
12. Delete the conflicting resources.
13. After you delete the conflicting resources, [retry the installation](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install).