/oci/. All operations involve network
I/O to the remote object store. Uses aioboto3 against OCI’s
S3-compatible API.
For credential setup, see OCI Setup.
Config
OCIResource(config) takes an OCIConfig object with the bucket name,
OCI tenancy namespace, region, and Customer Secret Key credentials.
The S3-compatible endpoint is auto-built from namespace + region
unless endpoint_url is supplied. Both READ and WRITE modes are
supported.
Filesystem Layout
The OCI resource maps object keys to virtual paths under the mount prefix. OCI “directories” are prefix-based — there are no real directory objects. For example, if bucketmy-bucket contains:
/oci/ exposes:
/oci/data/users.csv maps to OCI key
data/users.csv.
Cache
The OCI resource usesIndexCacheStore with index_ttl = 600
(10 minutes). Directory listings are cached for up to 600 seconds before
being refreshed from OCI.
Example
Shell Commands
The OCI resource supports the full set of shell commands since it operates on real file content (text, binary, JSON, CSV, etc.). Large files benefit from range reads to avoid downloading entire objects.Read Commands
Text Processing
File Operations
Path Utilities
Compression
Encoding
Data Format Support
Commands with format-specific variants for structured data files:
These variants auto-detect the format by extension and convert to
tabular text (CSV) for processing.
Use Cases
- AI agents accessing OCI data: Mount OCI buckets for agents to read and process datasets
- Data pipelines: Read and write OCI objects with shell-like commands
- FUSE mounting: Expose OCI buckets through a virtual FUSE mount for external tools