You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a current use case we want to use an Asset and set its dataAddress to allow proxyQueryParams. As an example consider the following, our Asset has a baseUrl of https://example.com and the user can use queryParams to request different underlying data like so: https://example.com?query=hello&id=123. The question now arises how the assets in EDC would support such a behaviour. After some research we found out that one can enable flags to enable certain behaviour on producer side. So in order to create an asset, one would need to enable proxyQueryParams like so:
But had no luck. In addition the documentation or openapi.yaml has no information on what could go into the "properties" section on how to control the "dataAdress" or "dataDestination" behaviour.
Why Is the Feature Desired?
In order to for developers to use the EDC to hook up any data source this part of the documentation is crucial
The text was updated successfully, but these errors were encountered:
Feature Request
More Documentation on Asset creation
Description
In a current use case we want to use an Asset and set its
dataAddress
to allowproxyQueryParams
. As an example consider the following, our Asset has a baseUrl ofhttps://example.com
and the user can use queryParams to request different underlying data like so:https://example.com?query=hello&id=123
. The question now arises how the assets in EDC would support such a behaviour. After some research we found out that one can enable flags to enable certain behaviour on producer side. So in order to create an asset, one would need to enableproxyQueryParams
like so:But how would the consumer now tell the producer which params to proxy to the dataAdress baseUrl ? I tried with the following request data:
But had no luck. In addition the documentation or openapi.yaml has no information on what could go into the "properties" section on how to control the "dataAdress" or "dataDestination" behaviour.
Why Is the Feature Desired?
In order to for developers to use the EDC to hook up any data source this part of the documentation is crucial
The text was updated successfully, but these errors were encountered: