feature: Move An APIExport From One Workspace To Another

[stevekuznetsov]

Feature Description

A company providing some service through some APIExport is acquired by another company. The acquiring company would like to continue providing the same service, but move the APIExport, controllers, etc, into their own workspace hierarchy.

Proposed Solution

We record the identity hash inside of an APIExport for exactly this reason - if another APIExport is created with the contents of the identity secret, the new APIExport owner can prove they have the trust of the folks who bound the previous APIExport. We need to think through how the transition works, though - how does a user re-write a binding?

Alternative Solutions

No response

Want to contribute?

• [ ] I would like to work on this issue.

Additional Context

No response