feat: discovery endpoint#5768
Merged
Merged
Conversation
wolf4ood
force-pushed
the
feat/5764_discovery_api
branch
from
fe31873 to
e4d6ffc
Compare
wolf4ood
force-pushed
the
feat/5764_discovery_api
branch
2 times, most recently
from
4f1abab to
d3e9b05
Compare
wolf4ood
force-pushed
the
feat/5764_discovery_api
branch
from
d3e9b05 to
bc4d7fe
Compare
jimmarino
approved these changes
May 22, 2026
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
2 participants
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.
What this PR changes/adds
Adds a management API for discovering the compatibiliy with a counter party.
The request accept either a:
counterPartyAddresscounterPartyIdResolvers are registered to be able given a request to resolve the
well-known/dspace-versionendpoint of the counter party.Once resolved the discovery service will fetch the supported protocol version of the counterparty and matching with the local profile supported. The response will return with profile to use and for which counterparty protocol path. Currently it does the match with the protocol version and the binding
Why it does that
Briefly state why the change was necessary.
Further notes
For having a more precise match. We could support in the dspace-version a new property called
profilewhich will allow us to match also the specific profile.Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Linked Issue(s)
Closes #5764
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.