#150 peering panel v2: one relationship card per peer (v0.6.21) #232
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/150-peer-cards"
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?
Collapses the two separate "keys you issued" / "instances you can send to" lists into a single relationship card per peer, joining the inbound key we issued them and the outbound side (URL + allow-lists) under one name so the two halves can no longer drift apart (#145).
Each card: issue/revoke the inbound key from within the card, inline edit of the send/receive allow-lists (PATCH, #176), a per-peer pause toggle (#176), test-connection, and remove. Orphan inbound keys surface as their own card with the existing warning. Backend was v0.6.20 (#176).
Closes #150.