This section explains how to use the
qq object_bridge_create command.Description
Test-only. Create a bridge filesystem rooted at an external object bucket. The cluster must have been created with the object_portals test option enabled.
Usage
qq object_bridge_create [-h] --bucket-uri BUCKET_URI --mount-path MOUNT_PATH [--key-prefix KEY_PREFIX] [--delimiter DELIMITER] [--access-key-id ACCESS_KEY_ID] [--secret-access-key SECRET_ACCESS_KEY] [--key-vault-hostname KEY_VAULT_HOSTNAME]
[--notification-queue-url NOTIFICATION_QUEUE_URL]
Flags
| Flag Name | Required | Description |
|---|---|---|
--bucket-uri
|
Yes | Full bucket URI. Examples: https://my-bucket.s3.us-west-2.amazonaws.com/ or https://myaccount.blob.core.windows.net/my-container |
--mount-path
|
Yes | Absolute path in the primary filesystem where the bridge will be mounted. The parent directory must already exist; the basename is created during bridge creation. |
--key-prefix
|
No | Optional prefix inside the bucket. Stored with a trailing "/". |
--delimiter
|
No | Object-key separator used to project bridge directories. Defaults to "/". |
--access-key-id
|
No | Access key for private S3 endpoints. Omit for AWS ambient credentials. |
--secret-access-key
|
No | Secret key for private S3 endpoints. Omit for AWS ambient credentials. |
--key-vault-hostname
|
No | Azure Key Vault hostname (e.g. my-vault.vault.azure.net) from which to fetch SAS tokens for an Azure Blob bucket. Mutually exclusive with --access-key-id/--secret-access-key. |
--notification-queue-url
|
No | URL of an SQS queue that delivers this bucket's object-change notifications. Omit to use cache expiry only. |