feat: index outbound exchange messages #401
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.
The
ExchangeCueDoeris hooked up to our 3902 parser so that any successfully parsed and saved exchanges get indexed in the DB afterwards.This PR hooks up the
Exchangerto the parsing call in/identifiers/{name}/exchangesso that the same happens for outbound exchanges.This means we can properly find exns we have sent using
/exchanges/query(this exists in KERIA but not Signify - we are using it on our Signify fork).@lenkan On
mainthis doesn't need to be applied to IPEX as it's usingparserinstead ofhby.psrbut you reverted that in your PR. Once we have aligned on how to handle that there, we can consolidate everything.