Azure Blob

Writes files to a container prefix. It does not create a Synapse table — use Synapse when you want SQL there.

Before you begin

Storage account name and container.
An account key or a SAS token. Store it in the environment.

bash

export AZURE_STORAGE_ACCOUNT_KEY="..."

Configure

PythonCLIYAML

python

from skippr import Config, DataSinkAzureBlob, EnvRef, Pipeline

cfg = Config.discover()
raw = cfg.data_sink(
    "raw",
    DataSinkAzureBlob(
        account_name="acmelanding",
        container="skipprd",
        account_key=EnvRef("AZURE_STORAGE_ACCOUNT_KEY"),
        prefix="events",
    ),
)
cfg.pipeline("events", Pipeline(data_source=cfg.get_data_source("sample"), data_sink=raw))
cfg.save()

bash

skipprd connect data-sink azure_blob \
  --pipeline events \
  --name raw \
  --account-name acmelanding \
  --container skipprd \
  --account-key '${AZURE_STORAGE_ACCOUNT_KEY}' \
  --prefix events

yaml

data_sinks:
  raw:
    AzureBlob:
      account_name: acmelanding
      container: skipprd
      account_key: ${AZURE_STORAGE_ACCOUNT_KEY}
      prefix: events

Options

Key	Type	Required/Default	Description
`account_name`	string	Required	Storage account
`container`	string	Required	Container
`account_key`	secret	Not set	Account key as `${ENV}`
`sas_token`	secret	Not set	SAS token as `${ENV}` (use instead of the key)
`prefix`	string	Not set	Blob prefix
`format`	string	Not set	Object format override

A retry overwrites the same blob.

How data lands

Blobs land under {container}/{prefix}/{namespace}/.

Troubleshooting

Symptom	Fix
Authentication failed	Export `account_key` or `sas_token` in this shell
Container missing	Create it, or grant the key rights to create it
403 on prefix	Narrow SAS to write on that prefix

Azure Blob ​

Before you begin ​

Configure ​

Options ​

How data lands ​

Troubleshooting ​

Next steps ​