feat: add dataset endpoint management api #3342
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.
What this PR changes/adds
Add
/dataset/request
endpoint on management apiWhy it does that
permit dataset fetch from the clients.
Further notes
CatalogRequest
to the standard, renamingproviderUrl
tocounterPartyAddress
as it was done pretty much in all the codebase, this needs to be done to the other APIs as well (renameproviderUrl
andconnectorAddress
tocounterPartyAddress
on management api #3343). This was done deprecatingproviderUrl
to avoid breaking changes.DspHttpRequestFactory
component, that moved the request creation responsibility away from the "delegate", going towards composition over extension. This could be done also on the "response" side, removing that abstract delegate at all and avoiding some duplication as well. (get rid ofDspHttpDispatcherDelegate
#3344)Linked Issue(s)
Closes #3281
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.