vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"params" : {
"bucket_name" : "cos-destination-en-bucket",
"instance_id" : "42e13636e-0548-41a0-a178-e95be28464773",
"endpoint" : "https://s3.us-west.cloud-object-storage.appdomain.cloud"
}
}









 ibmcloud event-notifications destination list 



* Action: List all Destination.

ibmcloud event-notifications destination list [--limit LIMIT] [--offset OFFSET] [--search SEARCH] [--instance-id INSTANCE-ID]
* Parameters to provide:

--limit LIMIT (int64)
: The page limit for paginated results.

The maximum value is 100. The minimum value is 1.

--offset OFFSET (int64)
: The offset for paginated results.

The minimum value is 0.

--search SEARCH (string)
: The search string for filtering results.

The maximum length is 100 characters. The minimum length is 0 characters. The value must match regular expression /[a-zA-Z0-9]/.

--instance-id (string)
: The unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.







 ibmcloud event-notifications destination get 



* Action: Get specific Destination.

ibmcloud event-notifications destination get --id ID [--instance-id INSTANCE-ID]
* Parameters to provide:

--id ID (string)
: The unique identifier for destination. Required.

The maximum length is 36 characters. The minimum length is 36 characters.
Message: The volume cannot be attached because the number of volume attachments would exceed the quota.

The quotas per instance are specified in [Quotas: Block storage volumes](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-quotasblock-storage-quotas).





 volume_attachment_update_invalid_request 

Message: The volume attachment could not be updated because the request is invalid.

The volume attachment could not be updated for either of these reasons:



* The boot volume's volume attachment cannot be renamed
* The boot volume's volume attachment delete_volume_on_instance_delete field cannot be set to true







 volume_capacity_max 

Message: The maximum volume capacity allowed is 2000 GB.

The volume capacity you specified exceeds the maximum volume capacity. Specify a value between 10 and 2000 GB. See the [IBM Cloud Block Storage for VPC](https://cloud.ibm.com/docs/vpc-on-classic-block-storage?topic=vpc-on-classic-block-storage-block-storage-about) documentation for accepted capacity ranges for a Custom profile.





 volume_capacity_missing 

Message: The required volume capacity value is missing in the request.

When you create a volume, you must specify a volume capacity based on this profile definition. For more information, see the [IBM Cloud Block Storage for VPC](https://cloud.ibm.com/docs/vpc-on-classic-block-storage?topic=vpc-on-classic-block-storage-block-storage-about) documentation.





 volume_capacity_zero_or_negative 

Message: The volume capacity should be greater than zero.

When creating a volume, the capacity value specified in the request must be a positive number between 10 GB and 2000 GB. See the [IBM Cloud Block Storage for VPC](https://cloud.ibm.com/docs/vpc-on-classic-block-storage?topic=vpc-on-classic-block-storage-block-storage-about) documentation for supported volume capacity values.





 volume_crn_account_id_mismatch
"endpoint" : "https://s3.us-west.cloud-object-storage.appdomain.cloud"
}
}









 ibmcloud event-notifications destination list 



* Action: List all Destination.

ibmcloud event-notifications destination list [--limit LIMIT] [--offset OFFSET] [--search SEARCH] [--instance-id INSTANCE-ID]
* Parameters to provide:

--limit LIMIT (int64)
: The page limit for paginated results.

The maximum value is 100. The minimum value is 1.

--offset OFFSET (int64)
: The offset for paginated results.

The minimum value is 0.

--search SEARCH (string)
: The search string for filtering results.

The maximum length is 100 characters. The minimum length is 0 characters. The value must match regular expression /[a-zA-Z0-9]/.

--instance-id (string)
: The unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.







 ibmcloud event-notifications destination get 



* Action: Get specific Destination.

ibmcloud event-notifications destination get --id ID [--instance-id INSTANCE-ID]
* Parameters to provide:

--id ID (string)
: The unique identifier for destination. Required.

The maximum length is 36 characters. The minimum length is 36 characters.
plan = "standard"
location = "eu-de"
service = "messages-for-rabbitmq"
resource_group_id = data.ibm_resource_group.resource_group.id
adminpassword = "password12"
members_memory_allocation_mb = 2048
members_disk_allocation_mb = 1024

service_endpoints = var.service_endpoints
}

You have to update the memory and disk allocation size in the Terraform configuration file as shown in the code block.

members_memory_allocation_mb = 3072
members_disk_allocation_mb = 3072

For more information, about configuring the memory and disk allocation for the database, see [IBM Cloud Database instance](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/database).





 How can I resolve cross-origin resource sharing (CORS) configuration issue while creating a cloudant instance? 

You need to own manager role for configuring cross-origin resource sharing (CORS) configuration to successfully apply the plan. You can only create an IBM Cloudant instance with the writer role. For more information, about IBM Cloudant instance access, see [roles](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-work-with-your-accountroles).

For example, to get the resource-controller.instance.create action you need Cloudant Platform editor or Administrator role. To configure the Cloudant instance feature such as cloudantnosqldb.sapi.usercors action you need the cloudant service manager role. For more information, about IBM Cloud cloudant, see [ibm_cloudant](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cloudant) resource.





 Can I increase or decrease timeouts while deleting Terraform resource? 

Yes, you can increase or decrease timeouts by using timeouts blocks within your resource block as shown in the example.
plan = "standard"
location = "eu-de"
service = "messages-for-rabbitmq"
resource_group_id = data.ibm_resource_group.resource_group.id
adminpassword = "password12"
members_memory_allocation_mb = 2048
members_disk_allocation_mb = 1024

service_endpoints = var.service_endpoints
}

You have to update the memory and disk allocation size in the Terraform configuration file as shown in the code block.

members_memory_allocation_mb = 3072
members_disk_allocation_mb = 3072

For more information, about configuring the memory and disk allocation for the database, see [IBM Cloud Database instance](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/database).
* How can I resolve cross-origin resource sharing (CORS) configuration issue while creating a cloudant instance?

You need to own manager role for configuring cross-origin resource sharing (CORS) configuration to successfully apply the plan. You can only create an IBM Cloudant instance with the writer role. For more information, about IBM Cloudant instance access, see [roles](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-work-with-your-accountroles).

For example, to get the resource-controller.instance.create action you need Cloudant Platform editor or Administrator role. To configure the Cloudant instance feature such as cloudantnosqldb.sapi.usercors action you need the cloudant service manager role. For more information, about IBM Cloud cloudant, see [ibm_cloudant](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cloudant) resource.
* Can I increase or decrease timeouts while deleting Terraform resource?

Yes, you can increase or decrease timeouts by using timeouts blocks within your resource block as shown in the example.
Status available
Attachment state attached
Capacity 8000
IOPS 24000
Bandwidth(Mbps) 3145
Profile general-purpose
Encryption key -
Encryption provider_managed
Resource group defaults
Created 2023-06-29T16:14:59+00:00
Zone us-east-1
Health State ok
Volume Attachment Instance Reference Attachment type Instance ID Instance name Auto delete Attachment ID Attachment name
data 0757_11f5db7f-35a1-4678-bcbd-c85204e09507 kj-test-ro false 0757-4dfc4384-c4b5-497e-bab3-6415f9c4d44b otp

Active true
Unattached capacity update supported false
Unattached iops update supported false
Busy false
Tags -
vsi-test1 0738-8b56da93-7990-4ccf-9dc5-5aee6a5f08f9

For more information about available command options, see [ibmcloud is volume-update](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referencevolume-update).







 Expand block storage volumes with the API 

You can expand existing data volumes by calling the Virtual Private Cloud (VPC) API. Make a PATCH /volumes request to increase the capacity of a volume that is attached to an instance.

You can't update the name of the volume and expand capacity in the same PATCH /volumes request. Make two separate PATCH/volumes requests.

This example request expands a volume with a capacity of 50 GB to 250 GB.

curl -X PATCH "$vpc_api_endpoint/v1/volumes/$volume_id?version=2022-02-25&generation=2" -H "Authorization: $iam_token" -d '{
"capacity": 250
}'

The volume status shows updating while the volume is being expanded. The current capacity is shown.

{
"capacity": 50,
File shares that are created from an [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesfs-tiers) can be expanded to the maximum size for its IOPS tier:



* A general-purpose, 3 IOPS/GB profile can be expanded up to 32,000 GB.
* A 5 IOPS/GB profile can be expanded up to 9,600 GB.
* A 10 IOPS/GB profile can be expanded up to 4,800 GB.



IOPS is automatically adjusted for tiered file share profiles, based on the size of the file share. For example, if you expand a share with a 5 IOPS/GB profile from 250 GB to 1,000 GB, it has a maximum IOPS of 5,000 IOPS (1,000 GB capacity x 5 IOPS). Because a 5 IOPS/GB file share can potentially expand to 9,600 GB, the max IOPS is adjusted to 48,000 IOPS. The capacity and the IOPS are immediately changed and you don't to restart the instance.

You can monitor the progress of your file share expansion from the UI or CLI. You can also use the [Activity Tracker](https://cloud.ibm.com/docs/vpc?topic=vpc-at-events) to verify that the file share was expanded. After a file share is expanded, you can't reduce capacity.





 Requirements 

The file share must be in a stable state before you can request that the capacity is increased.





 Limitations 

The following limitations apply to this release.



* File shares can expand, with the following restrictions:



* If the file share was created with a [Tiered IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesfs-tiers) that limits capacity to less than 32,000 GB, it can expand only to the allowed capacity for that tier.
You can also access the correct mount point through an API call: SoftLayer_Network_Storage::getNetworkMountAddress().
* How many volumes can I provision?

By default, you can provision a combined total of 700 Block and File Storage for Classic volumes. To increase your limit, contact your sales representative. For more information, see [Managing storage limits](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managinglimits).
* How many instances can share the use of a provisioned File Storage for Classic volume?

The default limit for number of authorizations per file volume is 64. To increase this limit, contact your sales representative.
* How many File Storage for Classic volumes can be attached to a single host?

That depends on what the host operating system can handle, it’s not something that IBM Cloud® limits. Refer to your OS Documentation for limits on the number of file shares that can be mounted.
* How many files and directories are allowed for specific file volume sizes? What is the maximum number of inodes allowed per volume size?

The number of files a volume can contain is determined by how many inodes it has. An inode is a data structure that contains information about files. Volumes have both private and public inodes. Public inodes are used for files that are visible to the customer and private inodes are used for files that are used internally by the storage system. The maximum number of files setting is 2 billion. However, this maximum value can be configured only with volumes of 7.8 TB or larger. The maximum number of inodes that can be configured on a volume is calculated by taking the total allocated volume size in KB and dividing it by 4. Any volume of 7.8 TB or larger reaches the maximum limit at 2,040,109,451 inodes.



Table comparison
Table 1 shows the maximum number of inodes that are allowed based on the volume size. Volume sizes are in the left column. The numbers of inodes (files and directories) are on the right.

 Volume Size Inodes 

 20 GB 5,242,880 
 40 GB 10,485,760
* --encryption-key: The CRN of the Key Management Service root key.
* --capacity: The capacity of the volume in gigabytes. Range 10 - 16000 for custom and general-purpose profile volumes, 10 - 9600 for 5iops-tier profile volumes, 10 - 4800 for 10iops-tier profile volumes.
* --tags: Comma-separated tags for the volume.
* --source-snapshot: ID or name of the snapshot to clone volume.
* --auto-delete: The attached volume is deleted when the instance is deleted. One of: false, true. (default: false).
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-volume-attachment-detach 

Delete one or more volume attachments, detaching volume from an instance.

ibmcloud is instance-volume-attachment-detach INSTANCE (VOLUME_ATTACHMENT1 VOLUME_ATTACHMENT2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* VOLUME_ATTACHMENT1: ID or name of the volume attachment.
* VOLUME_ATTACHMENT2: ID or name of the volume attachment.
* --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-volume-attachment-update 

Update a volume attachment.

ibmcloud is instance-volume-attachment-update INSTANCE VOLUME_ATTACHMENT [--name NEW_NAME] [--auto-delete true | false] [--output JSON] [-q, --quiet]



 Command examples
The available plans include Lite and Standard. When you select a plan, Capacity displays, and the Cost estimator shows the monthly charge for the selected plan. By default, the [Lite plan](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-ibm-cloud-publiclite-plan) is selected.



 Lite plan 

The Lite plan is free, and is designed for development and evaluation purposes. All of IBM Cloudant's functions are included, but Lite plan instances have a fixed amount of provisioned throughput capacity and data storage. The provisioned throughput capacity is fixed at 20 reads per second, 10 writes per second, and 5 global queries per second, and data storage is capped at 1 GB.

Storage usage is checked daily. If you exceed your 1-GB storage limit, requests to the IBM Cloudant instance receive a 402 status code with the following error message, Account exceeded its data usage quota. An upgrade to a paid plan is required. A banner also appears on the IBM Cloudant Dashboard. You can still read and delete data. However, to write new data, you have two options. First, you can upgrade to a paid [Standard plan](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-ibm-cloud-publicstandard-plan), which removes the write limitation immediately. Alternatively, you can delete data so that your total storage falls under the 1-GB limit and wait until the next daily storage check runs for your instance to allow writes again.

If you want to store more than one GB of data, or be able to scale provisioned throughput capacity, move to the [Standard plan](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-ibm-cloud-publicstandard-plan).

You're limited to one IBM Cloudant Lite plan instance per IBM Cloud account. If you already have one Lite plan instance, you can't create a second Lite plan instance, or change a Standard plan instance to a Lite plan. If you try, you see the following message.
What is the maximum state file size of import? 

The terraform.tfstate file size must be less than 2 MB. When you create workspace from an existing Terraform state file, the terraform.tfstate file size must be less than 2 MB. Greater than 2 MB state file size is not supported in the Schematics. You will see an error message with 413 Request Entity Too Large error when creating a new Schematics workspace.





 How do I fix authentication errors when using the API? 

You need to create the IAM access token for your IBM Cloud Account. For more information, see [Get token password](https://cloud.ibm.com/apidocs/iam-identity-token-apigettoken-password). You can see the following sample error message and the solution for the authentication error.

Error: Request fails with status code: 400, BXNIMO137E: For the original authentication, client id 'default' was passed, refresh the token, client id 'bx' is used.

The [IAM API](https://cloud.ibm.com/apidocs/iam-identity-token-apigettoken-apikey) documentation shows how to create a default token. You can use the refresh token to get a new IAM access token if that token is expired. When the default client (no basic authorization header) as described in this documentation. The refresh_token cannot be used to retrieve a new IAM access token. When the IAM access token is about to be expired, use the API key to create a new access token as listed.



1. You need to create access_token and refresh_token.

export IBMCLOUD_API_KEY=<ibmcloud-api_key>
curl -X POST "https://iam.cloud.ibm.com/identity/token" -H "Content-Type: application/x-www-form-urlencoded" -d "grant_type=urn:ibm:params:oauth:grant-type:apikey&apikey=$IBMCLOUD_API_KEY" -u bx:bx
2.
For more information about creating security and compliance goals, see [Defining rules](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-rules-define&interface=ui) in the Security and Compliance documentation.





 Limitations in this release 

The following limitations apply to this release of File Storage for VPC.



* File share size cannot be increased after it is created.
* Previous profiles are not supported when you provision a new file share, which is based on the dp2 profile. However, earlier version file shares can continue to use existing profiles.
* Restricting file share access to specific virtual server instances and data encryption in transit is available only for shares that are based on the dp2 profile.
* Windows operating systems are not supported.
* Minimum capacity is 10 GB per file share.
* Maximum capacity is 32,000 GB per file share.
* No data retention policy exists for deleted file shares. You cannot undelete a file share after you delete it.
* Up to 256 hosts per zone per VPC can be concurrently connected to a single file share.







 Related information 

For more information about the IBM Cloud VPC, see [Virtual Private Cloud](https://www.ibm.com/cloud/learn/vpc).

For more information about VPC, see [Getting started with Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).





 Next steps 



* [Plan for creating file shares and mount targets](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-planning).
* [Create a file share and mount targets](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create).
0757-6757e676-0bf5-4b79-9a5b-29c24e17420c otp1 demo-volume-update attached data 0757-6757e676-0bf5-4b79-9a5b-29c24e17420c-bxsh7 true
0757-af470ade-9d5c-491e-97b2-f000ed4ee49b scheming-tipper-shivering-decrease kj-test-ro-boot-1629867631000 attached boot 0757-af470ade-9d5c-491e-97b2-f000ed4ee49b-fc4tl true

For more information about available command options, see [ibmcloud is instance-volume-attachments](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referenceinstance-volume-attachments).





 Create a volume attachment JSON 

When you provision a virtual server instance from the CLI and create a Block Storage for VPC volume as part of the process, you can specify a volume attachment JSON. The volume attachment JSON, specified in the command or as a file, contains the volume parameters.

In the CLI command that you use to [create an instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=cli), you specify the --volume-attach option and the volume JSON file. For example, --volume-attach @/Users/myname/myvolume-attachment_create.json.

The following example shows the content of a volume attachment JSON file that defines a custom volume and specifies user tags.

[
{
"name": "myvolume-attachment",
"delete_volume_on_instance_delete": true,
"volume": {
"name": "myvolume",
"capacity": 100,
"iops": 1000,
"profile": {
"name": "custom"
.rev("4-1a0d1cd6f40472509e9aac646183736a")
.build();

DocumentResult response =
service.deleteAttachment(attachmentOptions).execute()
.getResult();

System.out.println(response);

from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.delete_attachment(
db='products',
doc_id='small-appliances:100001',
attachment_name='product_details.txt',
rev='4-1a0d1cd6f40472509e9aac646183736a'
).get_result()

print(response)

deleteAttachmentOptions := service.NewDeleteAttachmentOptions(
"products",
"small-appliances:100001",
"product_details.txt",
)
deleteAttachmentOptions.SetRev("4-1a0d1cd6f40472509e9aac646183736a")

documentResult, response, err := service.DeleteAttachment(deleteAttachmentOptions)
if err != nil {
panic(err)
}

b, _ := json.MarshalIndent(documentResult, "", " ")
fmt.Println(string(b))

const { CloudantV1 } = require('@ibm-cloud/cloudant');

const service = CloudantV1.newInstance({});

service.deleteAttachment({
db: 'products',
docId: 'small-appliances:100001',
attachmentName: 'product_details.txt',
rev: '4-1a0d1cd6f40472509e9aac646183736a'
For more information about troubleshooting jobs, see [Troubleshooting - Why can't I submit a job run?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-jobrun-submit-fails-cli).







 Function limits 

The following table lists the limits for Functions.



Function limits

 Category Maximum Need to extend the maximum? 

 Length of runtime 120 seconds 
 Code size 1 MB compressed, including base64 overhead [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Invocation URI size 1.0 [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Request body size 2048 bytes [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Request header size 5 MB [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Response body size 4 KB [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Timeout 600 seconds [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 







 Project quotas 

The maximum number of projects that you can create per region is 20.

The maximum number of projects includes projects that are active and any projects that are not permanently deleted. When you delete a project, the project is soft deleted, and can be restored within 7 days before it is permanently deleted. Use the console or the CLI to display soft-deleted projects. For more information, see [deleting a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-projectdelete-project).