Alan-Jowett / LexonGraph / 27840283386

81%

push

github

Add Azure Blob block store backend (#115)

* Add Azure Blob block store backend

Introduce an Azure Blob Storage BlockStore implementation over container SAS URLs, add its specification package and validation coverage, and update workspace metadata.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Address Azure backend review feedback

Align reqwest with the existing workspace dependency, add default HTTP timeouts, restore connection pooling, and avoid cloning canonical block bytes on the success path.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Redact SAS URLs from Azure backend errors

Use reqwest error redaction so BackendFailure messages do not expose SAS query parameters when HTTP request or body-read operations fail.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Tighten Azure SAS and enumeration rules

Reject empty SAS query strings, clarify malformed block-blob candidate semantics in the Azure backend spec package, and include offending blob names in enumeration decode failures.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Refine Azure SAS validation and docs

Require a non-empty SAS signature parameter at construction, cover non-SAS queries in tests, clarify diagnostic error exposure in the Azure design spec, and qualify the README backend summary.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix Azure mock server lifecycle and XML escaping

Move mock-server shutdown to the external server handle lifecycle, and XML-escape listed blob names so the mock matches Azure listing semantics.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Clarify Azure shard-mismatch enumeration failures

Document that shard-prefix mismatches are malformed recognized block-blob candidates that fail enumeration explicitly, and add validation coverage for that case.

Co-authored-by: Copilot <223556219+Copilot@us... (continued)

286 of 347 new or added lines in 1 file covered. (82.42%)

20092 of 24676 relevant lines covered (81.42%)

78734.77 hits per line