Kept (deleted) accounts can't be managed from the console. With account retention set, a deleted account is kept for the period and its name and addresses stay reserved, but the only way to restore it or destroy it early is a raw inbuxa:DeletedAccount/get / /set call. Someone on the forum (https://community.coffeylabs.org/t/232) got stuck there and started looking at RocksDB.
Add a Deleted Accounts page, next to Accounts:
list from inbuxa:DeletedAccount/get (name, addresses, deleted at, kept until, tenant)
Restore, which needs a new password (update: {restore: true, password}), with the same password checks as account create
Destroy now, with a confirm that says it can't be undone (destroy). Accounts under a legal hold are refused by the server, so show that error as-is.
only shown to admins with the account permissions the server checks (get: sysAccountGet, restore: sysAccountCreate, destroy: sysAccountDestroy)
Related: when a delete comes back objectIsLinked, the Domains page should show the server's description of what's linked rather than a blank or generic error. The server side of that is in inbuxa-server.
Kept (deleted) accounts can't be managed from the console. With account retention set, a deleted account is kept for the period and its name and addresses stay reserved, but the only way to restore it or destroy it early is a raw `inbuxa:DeletedAccount/get` / `/set` call. Someone on the forum (https://community.coffeylabs.org/t/232) got stuck there and started looking at RocksDB.
Add a Deleted Accounts page, next to Accounts:
- list from `inbuxa:DeletedAccount/get` (name, addresses, deleted at, kept until, tenant)
- Restore, which needs a new password (`update: {restore: true, password}`), with the same password checks as account create
- Destroy now, with a confirm that says it can't be undone (`destroy`). Accounts under a legal hold are refused by the server, so show that error as-is.
- only shown to admins with the account permissions the server checks (get: sysAccountGet, restore: sysAccountCreate, destroy: sysAccountDestroy)
Related: when a delete comes back `objectIsLinked`, the Domains page should show the server's description of what's linked rather than a blank or generic error. The server side of that is in inbuxa-server.
Done in #173, with the menu link from inbuxa/inbuxa-server#315. Management > Directory > Deleted Accounts lists kept accounts and restores one or destroys it now. It goes out with the next 27.1 rc of the console and server.
Done in #173, with the menu link from inbuxa/inbuxa-server#315. Management > Directory > Deleted Accounts lists kept accounts and restores one or destroys it now. It goes out with the next 27.1 rc of the console and server.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Kept (deleted) accounts can't be managed from the console. With account retention set, a deleted account is kept for the period and its name and addresses stay reserved, but the only way to restore it or destroy it early is a raw
inbuxa:DeletedAccount/get//setcall. Someone on the forum (https://community.coffeylabs.org/t/232) got stuck there and started looking at RocksDB.Add a Deleted Accounts page, next to Accounts:
inbuxa:DeletedAccount/get(name, addresses, deleted at, kept until, tenant)update: {restore: true, password}), with the same password checks as account createdestroy). Accounts under a legal hold are refused by the server, so show that error as-is.Related: when a delete comes back
objectIsLinked, the Domains page should show the server's description of what's linked rather than a blank or generic error. The server side of that is in inbuxa-server.Done in #173, with the menu link from inbuxa/inbuxa-server#315. Management > Directory > Deleted Accounts lists kept accounts and restores one or destroys it now. It goes out with the next 27.1 rc of the console and server.