feat: new role for schema discovery #920
Merged
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.
To be honest, I'm not sure what to call this new role.
It's to address #886. This role is meant to allow a controller to designate a service endpoint (which may be on a different URL than the controller/agent) for discovery of schemas. Perhaps it could be used for other things, which is why I tried to leave it broad as
indexer
- like an index of OOBIs (or other things, like public ACDCs...) by SAIDs.Open to suggestions.
Tested with KERIA/Signify to add a new loc scheme and end role auth where the
cid=eid
, and the service endpoint appears in the OOBI formathttp://keria.com/oobi/<cid>
.