hivectl, hive-c0re: remove dead matrix create-user/promote-user/reset-password
Human matrix accounts come from SSO, not hivectl. Matrix homeserver admin will come from authelia's admins group (sync tracked in #4585); password reset moves to swarm level (#4798). promote-user and reset-password were already broken from the hive: the hive's sender account has no admin sender to call the admin room with, only the swarm's does. Removes the three hivectl matrix verbs, their HostRequest variants, their hive-c0re handlers, and the admin-room helpers (discover room id, send-and-poll, event-id extraction, password/success parsing) that only they used. sync-admin and invite are unchanged. Refs #4585
This commit is contained in:
parent
69ae23f801
commit
93bbec015f
12 changed files with 37 additions and 748 deletions
|
|
@ -286,11 +286,12 @@ hivectl matrix sync-admin
|
|||
# Invite the operator to the hive Space (and optionally to rooms)
|
||||
hivectl matrix invite mara
|
||||
hivectl matrix invite @mara:yourserver --room '#hive-chat:yourserver'
|
||||
|
||||
# Promote the operator to homeserver admin if needed
|
||||
hivectl matrix promote-user mara
|
||||
```
|
||||
|
||||
The operator's own matrix account comes from SSO, not `hivectl` — matrix
|
||||
homeserver admin should eventually come from membership in authelia's
|
||||
`admins` group; nobody has built that sync yet.
|
||||
|
||||
ruth's own matrix account comes from the swarm, like every agent's:
|
||||
`swarm-controller` creates it within five minutes of her holding a store
|
||||
identity (step 1), and her matrix daemon reads its token from the store.
|
||||
|
|
|
|||
Loading…
Reference in a new issue