Skip to content

Object store

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade D · dataset: Files (real PDFs, images, video and sheets) · type objectstore

What it is

Objects in an S3, GCS or Azure bucket. In the test estate it holds a finance invoice register. The connector reference is Files and object storage.

Grade

D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typeobjectstore
Other spellings that resolveobjectstorage, s3, awss3, aws, amazons3, minio, ceph, objectd, gcs, gcp, google, googlecloudstorage, googlestorage, azure, azblob, azureblob, azureblobstorage, blobstorage, abs
Settingsprovider, bucket, prefix, region, endpoint, account, use_tls
Credentialsaccess_key, secret_key, session_token, service_account_json, account_key, sas_token

The test connection

Finance exports

SettingTest value
providers3
bucketquillmere-exports
prefixfinance/
regionus-east-1
endpointhttps://s3.quillmere.invalid
use_tlstrue

Credentials: access_key, secret_key. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. Download objectstore.zip and unzip it. It holds objectstore/finance/invoice_register.csv and expected.json.
  2. Upload objectstore/finance/ to a bucket named quillmere-exports in an S3-compatible store you own (MinIO is one open-source option).
  3. For a new connection, prefer files with provider s3.

What FACE finds

FACE’s object-store connector lists the bucket. There is no catalogue.

DatasetKindDomainPrimary keyRowsFields
s3://quillmere-exports/finance/.invoice_registertext/csvfinanceinvoice_id245

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 3 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
carrierinvoice_register.carrier_idd365, document, files, guidewire, mysql, postgres, redshift, sharepoint, tms, yms
invoiceinvoice_register.invoice_idd365, files, mysql, redshift
shipmentinvoice_register.shipment_idbigquery, d365, databricks, document, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, postgres, redshift, salesforce, sap, servicenow, sharepoint, tms, whs, yms

It holds no evidence for the six planted anomalies. It is context: it makes the shared keys resolve.

See all connectors at once for the walkthrough across every source.

Download

This is one of 25 zips: the 7 streaming types ship as replay recordings instead.

What is in the zip
  • objectstore/finance/invoice_register.csv
  • objectstore/expected.json

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.