Skip to main content
Version: 1.9.0

Azure blob upload config

Overview​

Saving a company BLOB_STORAGE upload config stores both the renewable SAS fields and the fields boxes before 4.35 still read.

How it works​

PATCH /admin/company/upload-config runs normalizeBlobUploadSettings when the provider is BLOB_STORAGE.

  • A Retool payload (containerUrl + sasToken) is kept, and sasUrl plus container are filled from it.
  • An account SAS (https://<account>.blob.core.windows.net/?sv=...) uses the container form field.
  • A container SAS uses the container in the URL path.
  • A URL that points at a specific blob is rejected.

Key files​

  • app/util/normalizeBlobUploadSettings.js — Derive both config shapes
  • app/routes/admin.js — Normalize on save
  • test/normalize-blob-upload-settings.js — Account SAS, container SAS, and Retool payload

Technical decisions​

  • Keep sasUrl and container so older boxes keep uploading after a token renewal.
  • Prefer containerUrl and sasToken when both shapes are present, so a renewal overwrites the token the current box uses.

Known issues​

  • Existing documents are not rewritten. Only the company upload config changes.

Next steps​

  • Drop sasUrl and container once every box is on 4.35 or later