Skip to content

Land the attachments-storage QA scratch fixture (qa_vault/qa_shared/qa_nofiles + two personas) as permanent #7670

Description

@huangyiirene

Symptom

The attachments-storage area has no private, files-enabled parent on stock showcase — the only enable.files object is public_read_writeand readable via the showcase everyone baseline. That would force blocked(fixture) on the entire authz core of this area every run.

Root cause

Not a defect — a missing fixture. The run closed the gap at runtime, touching no repo file: POST /api/v1/packages, then PUT /meta/objects/qa_vault?package=… with sharingModel:'private', plus qa_shared (public_read) and qa_nofiles (no enable.files); and two real member personas provisioned via sign-up + a runtime permission-set / position binding. This should be landed as a permanent fixture (docs/qa/platform-checklist fixtures) so the area does not need re-provisioning each run.

Reproduction

Run any attachments-storage authz item on stock showcase → no private files-enabled parent exists → blocked(fixture) unless the scratch objects + two personas are provisioned by hand first.

Source

Extracted from the QA run #7635 (framework 92f26f7, console 6314e87f).

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions