Skip to content

[quality-keeper] B2 standards failure #19

Description

@sophiecarreras

Summary

This repo fails one or more mandatory B2 standards checked by /b2-doctor.

The three standards are:

  1. S3-compatible API used as the default (not the native B2 API)
  2. Custom user-agent set on every S3 client
  3. Standardized B2_* env var names: B2_APPLICATION_KEY_ID, B2_APPLICATION_KEY, B2_BUCKET_NAME, B2_REGION, B2_PUBLIC_URL_BASE

Evidence

Run /b2-doctor <repo-path> for the exact per-repo failure reason.

Why it matters

These standards ensure consistent, auditable B2 usage across all sample repos.

Suggested fix

Run /b2-doctor to identify the exact failure, then fix to match the standard.

Acceptance criteria

  • B2_DOCTOR: PASS in the next quality-keeper run

Filed by quality-keeper (2026-06-19). Migrated from backblaze-labs/demand-side-ai#371.

Metadata

Metadata

Assignees

No one assigned

    Labels

    B2 SDKSDKs team (quality-keeper routing): security, B2 standards, unenforced-drift findings

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions