Provision and erase a workspace’s integration-area records
What It Does
Workspace lifecycle calls bounded participants rather than deleting all configuration in one transaction. Provisioning seeds a default calendar. Purge removes database records in dependency order but does not establish destruction of every external secret or stored provider object.
The Flow
When Something Fails
The lifecycle job can retry the failed step. Workspace preparation can wait for the initial calendar. Return the failed seed step for retry. No successful seed is duplicated and a deliberately deleted seed is not restored. Retry the failed lifecycle batch. Earlier committed batches leave the workspace partly removed. A failed batch is retried independently. Undeclared credential secrets and stored provider bodies, payloads and archives remain. Retry failed database purge batches. Handler secrets remain because the service cannot enumerate and remove them. Retry an incomplete or failed batch. Other participant batches can already have committed.
Open Design Questions
Product must decide how workspace deletion removes retained handler and connection secrets, provider bodies and payloads, and execution archives without expiry.