Add support for nested query parameters
Haim Natan
Using the custom ocean integration, we want to get jfrog repositories that require a query parameter to be populated as a nested Endpoint.
This want to query https://jfrog-platform.eu.aws.rccad.net/artifactory/api/repositories?project={project}
We want to have the ability to get the project from another endpoint just like we are doing on the nested endpoint path parameters.
D
Dan DEVAUCOUP
Hello Haim, Gal, I was checking the work done on the version 0.6.72-rc1.
Great job, it does work great.
I have a last thing missing for my use case is: to have access to the dynamic param in the payload sent to Port (also applicable with path params).
Usually the dynamic param is key, but unfortunately it is not part of the payload sent by the backend, so the result in Port is there is payload but no way to link to it the correct resource as the key as been lost.
Example of use case is SonarQube API: https://next.sonarqube.com/sonarqube/web_api/api/alm_settings/get_binding
The project key is a dynamic param, but not present in the final payload. I'm not sure there is a solution for that.
M
Maya Margalit
Merged in a post:
Add support for dynamic resolution for query_params in custom ocean integration
B
Benoit MENARD
We need to export from API endpoint, but the API endpoint support mainly query_parameter instead of path_parameter.
We need for example to do https://example.com/api/test?project={project} where {project} is fetch by a previous call
We want to be able to read the {project} from another endpoint, the same that can be done with path_parameters.