Questions¶
Each page here is titled with a question and answers it in its first paragraph, in terms that hold for anyone. The rest of the page says how goat handles the same thing and links to the design documents in goatcore.
Status words on these pages mean what they mean in the design documents: built is code that exists and runs, designed is decided and not implemented.
| Question | Topic |
|---|---|
| How do I change Zenoh access rules without a restart? | Zenoh access control |
| Can SPIRE run on a multi-master database? | SPIRE datastore and high availability |
| What do you give up with brokerless pub/sub? | Pub/sub without a broker |
| Why was my Zenoh publish silently dropped? | Finding a denied or lost write |
| Does a WireGuard mesh keep working when the management server is down? | Mesh control plane outage |
| How do I use certificate identity to control who can publish in Zenoh? | Certificates as pub/sub identity |
| How do two organizations share pub/sub data without sharing a certificate authority? | Federation between trust domains |
| How should a command-line tool explain its errors? | Error codes and interpretation |