Skip to content

DRAFT: POC to validate if a top-level group is isolated to be migrated to an Organization

Dylan Griffith requested to merge poc-organization-isolation-based-on-model-associations into master

What does this MR do and why?

Related to #394800 (closed) this POC shows how we might apply consistent sharding keys to traverse all the way down from namespace -> project -> all data related to all projects ... and therefore validate that all the records are indeed isolated to one top level namespace and would be safe to migrate to a new organization.

This is complementary to !133576 (closed) which would simplify all the logic for figuring out the parent record as we could just always assume that every model has a project_id or namespace_id and this is the parent.

Screenshots or screen recordings

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Dylan Griffith

Merge request reports