Repository navigation
driver.query and driver.health (M1): the application query and driver health - #53
Merged
Merged
Conversation
…th (M1) driver.query sends the engine's query verb as a command into the running driver's subscriber channel and prints the shim's instances; an LDAP DN is converted to the slash form the verb takes. Proven on edir3 through the Loopback driver. driver.health reads what the Driver Health job records on the driver (DirXML-uiXMLSmall), the health configuration on its manifest and the set's health jobs; clear removes the recorded status. Grounded on the job's own code (docs/console-gaps.md §10). The main usage now lists job.* and rbe.* too. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
Author
|
Merged into master and released as 0.23.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Phase M1 of docs/console-gaps.md (gaps G9 and G7), §10 of the note.
driver.query— the console'squeryValues: the engine's query verb goes as a command into the running driver's subscriber channel (the same door asdriver.submit) and the shim's<instance>s come back, as text or JSON. Options:--class,--scope subtree|subordinates|entry,--dn(an LDAP DN is converted to the slash form the verb takes, found the hard way on the first live try),--association,--search name=value…,--read-attr A…ornonefor a match test. A stopped driver is refused up front. Gated light and audited. Proven on edir3 through the Loopback driver: a search by CN returned the user with Surname and Given Name; an entry-scope query with--read-attr nonereturned the bare instance.driver.health [clear]— grounded on the Driver Health job's own code (ckdrvhealthjob.jar): the job evaluates each driver's<health-config>from itsDirXML-ConfigManifestand writes the verdict per server to the driver'sDirXML-uiXMLSmall. The command prints the last state per server (and each custom state), the configured states with condition-group and action counts, and the set's health jobs with whether the driver is in scope.clearremoves the recorded status, which is what the console'sclearDriverHealthStatusamounts to. No lab driver carries a health configuration, so the parsing is tested against the job's document shapes and live only for the empty case.Also:
job.*andrbe.*were missing from the main usage text; added.Tests: four new cases in OperateTest (query build and parse, running-driver refusal and read-none, health read, health clear). Full suite and
bin/ci-portable.shgreen. edir3 unchanged (the Loopback driver was started for the query and stopped again).Left for later: the health configuration in the tree (the manifest is not modelled), the web's "ask the application" on the Objects tab.
🤖 Generated with Claude Code