This section explains how to use the qq object_portal_create_bridge command.

Description

Create a bridge filesystem rooted at an external object bucket.

Usage

qq object_portal_create_bridge [-h] --bucket-uri BUCKET_URI --mount-path MOUNT_PATH [--key-prefix KEY_PREFIX] [--delimiter DELIMITER] [--key-vault-hostname KEY_VAULT_HOSTNAME] [--notification-queue-url NOTIFICATION_QUEUE_URL] --protocol-access
    {READ_WRITE_EXPORT,READ_ONLY} --metadata-import {OFF,AUTO}

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, matched against object keys as it is written. Must end with the delimiter. An empty prefix is refused; omit this option to bridge the whole bucket.
--delimiter No Object-key separator used to project bridge directories. Defaults to "/".
--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.
--notification-queue-url No URL of an SQS queue that delivers this bucket's object-change notifications. Omit to use cache expiry only.
--protocol-access Yes READ_ONLY rejects protocol data and namespace writes to the bridge while the bucket keeps converging; file attributes stay writable. READ_WRITE_EXPORT leaves both writable and requires bucket versioning. Immutable after creation.
--metadata-import Yes Import file-mover object metadata (ownership, permissions, ACLs, timestamps) onto bridge inodes. AUTO translates objects matching a known mover dialect; OFF inherits everything from the parent directory. Immutable after creation.