447 json schema #479
Merged
447 json schema #479
Conversation
This file contains 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
robot-ranger
force-pushed
the
447-json-schema
branch
from
80afa20 to
68c1a2c
Compare
wsobel
approved these changes
Jul 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 includes a json schema supporting json-formatted agent config files.
I did all the research i could to find as many undocumented parameters I could, and i found a few. However, the following appear in source but are undocumented in the readme:
The above are in the json schema but missing details.
If there are docs (description, acceptable inputs) for the above, i can add them before merging.
I also cleaned up and did a little organizing on the README. found some duplicate docs, organized a new section "Agent-Adapter Protocols" with sub sections for SHDR v2, MQTT Ingest, Heartbeat and HTTP/REST