v0.6.390: federated shares in the admin Shares list, administrator stop, server removal (#1071) #1080
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ab1071"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #1071.
o:<providerId>), with a Federated type filter, server search, the CSVserver,acceptedcolumns, a federated count in the PDF, and in review counts. An unreadable ledger answersfederated-unreadableand locks Export and Mark as reviewed.share-admin-revokeaudit, an owner bell and the Ended line "Ended by an administrator". The other server is told in the background.server-removed, oneshare-endedaudit record per share, a bell, an Ended line and a background notice. The dialog counts shares and owners when it opens.ocm-share-sendandocm-share-endare always recorded (admin tier), with notes naming the share id and the other address.audit-tiersis written at every start. The #1072 verbs are registered.share-not-live; the bell no longer stylesshare-admin-revokeditems as failed.Reviewed per wave (W1-W3) plus a final review with adversarial probes; all findings fixed or in the backlog.
T3 of ab1071 (spec 5, 6.2, 7.1): EndFederatedShare / endFederatedSet end a set of federated shares out in one ledger pass (read, EndOut, one read-back with a re-end of records live again, audit share-admin-revoke, activity, INFO, one OCM.Ended call, tombstones except for an earlier account's). DELETE /api/v1/admin/shares/o:<pid> and the bulk stop route through it. ocmServerRemove writes one share-ended per share out, owner tombstones (reason server-removed), the ocm-server-remove note counts and an INFO, and hands the ends to OCM.Ended instead of notifying on the request. The bell folds share-admin-revoked per {at, sub, server} with sub federated and providerId when it counts one. wireOCMFollow sets OCM.Ended to the background sender. TestOCMNotifySecret1057 changed (plan T3): the removal's SHARE_UNSHARED now goes through an ocm.Unsharer wired as OCM.Ended (Wait before reading the peer); the ended records end with Told "yes" instead of "pending".