Skip to content

Add live legacy-to-v2 Airlock migration regression coverage #5129

Open

Description

@JayDoubleu

Current Airlock tests create v2 workspaces. They do not prove safe migration of an existing legacy workspace or preservation of its data.

Current position

Item Status and evidence
Implementation No implementation PR yet.
Position Deferred coverage gap. No legacy-to-v2 migration case or live result is available.
Existing evidence #5136 records fresh-v2 validation. It is not migration evidence.

Scope

  • Create a disposable legacy workspace with representative import/export data.
  • Upgrade core and workspace through the supported procedure while retaining legacy storage.
  • Exercise the migration endpoint, version transition and repeated invocation where supported.
  • Check legacy behaviour before opt-in, v2 behaviour afterwards, data preservation and workspace access boundaries.

Remaining work

  • Implement the migration case after the Porter upgrade coverage in #5128.
  • Verify legacy storage removal only after every affected workspace has migrated.
  • Record upgrade limits, recovery and cleanup.

Related earlier work: #5048, #2727.

Related work

Parent: #5124.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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