Add some connectivity diagnostics infrastructure #68
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds several pieces of diagnostics functionality. It might be helpful to read the commits in order, but the new user-facing features are:
librarian check-connections
, intended to be run from a Librarian store host. This will look at all of the Librarian connections defined in~/.hl_client.cfg
and attempt to connect to each one. For each connection, it will ask for a list of all of its (available) stores and see if it can connect to them./connectivity-check
, accessible through the Admin menu, will run the above connectivity check on all stores attached to the Librarian server. This basically validates that all of the stores on this Librarian know how to talk to all of the stores on the other Librarians that this Librarian is aware of.No user-facing documentation or tests; this is about as much time as I can spend on this stuff this week.
Edit: BTW, I tested this stuff by fooling around on
folio2
. Not exactly a torture test but I think it will all work?