Skip to content

Add Airlock submitted-file integrity validation #5264

Open

Description

@JayDoubleu

Add direct checks that Airlock preserves submitted file contents through review and approval.

The draft-deletion checks from #5181 are merged through #5255. They confirm that the old draft SAS stops accepting writes, the draft container is absent, and the submitted container has the expected metadata. They do not read the submitted file contents or compare their hashes.

This issue tracks additional test coverage. No content-integrity defect is confirmed by the existing evidence.

Existing evidence

Targeted Airlock validation passed both selected cases at 1cec703. This establishes the recorded deletion and review-VM results, not the content checks below.

Acceptance criteria

  • Define the point at which submission fixes the accepted file contents.
  • Upload a known test file and record its SHA-256 hash and expected file list.
  • Read the submitted copy and compare its contents and file list with the expected values.
  • Exercise writes, overwrites and deletions through the old draft SAS during the asynchronous handover and after draft deletion.
  • Verify that these attempts cannot change the accepted submitted copy after the defined submission point.
  • Compare file contents during review and after approval or transfer.
  • Record the tested revision, live Azure run and terminal cleanup evidence. Keep API deletion and physical resource removal distinct.

Parent: #5124.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions