Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.| Comment | File | Size | Author |
|---|---|---|---|
| #4 | interdiff-1.txt | 1.1 KB | spheresh |
| #4 | 3015724-2.patch | 4.39 KB | spheresh |
Comments
Comment #2
spheresh commentedThe patch adds a field that allows you to add a flag to delete the workspace.
Similar issue to a multiversion module should be merged before this patchAllows to set a delete source flag if replication ends with success.
Comment #3
jeqq commentedComment #4
spheresh commentedComment #5
jeqq commented@spheresh What's the context of this issue? If it's meant to work similarly to "archive workspace" feature then it's a bad idea, that because replication results might not be ideal. We can get success replication status but in reality there might be some changes that doesn't get replicated (the causes can be different), if you delete the workspace then you lose all the content attached to that workspace and the workspace itself - this is Critical, you can leave both source and target in a broken state, only database backup would help.
Deleting workspaces should remain as it is - to be deleted as operation on the Workspace list page. This involves more consciousness from the person who deletes the workspace.
In your case, if you want the workspace to disappear from the UI and be deleted after successful replication, then it should consist from 2 steps: first - archive the workspace on successful replication and second - delete the workspace from UI, on the Archived workspaces list page (there is not the option to delete it there, but it can be added as operation).
Comment #6
l0ke