Secrets Manager - Split Organization
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
As discussed in Slack, in addition to moving an organization, we'll need to be able to split an organization into component pieces.
This will require splitting the data within a namespace, even if we use namespaces for each component of the hierarchy: pipelines auth methods only exist at the top-level namespace and so need to be manually split.
We would have to incur significant reorganization of data (pre-launch) if we want to use namespace-scoped auth & policies.
That said, it would theoretically allow existing move operation semantics to work, just with much, much higher scale (as every group and/or project moved would incur a separate move, versus an organization which would currently be a single move).