Low Code CDK - add parameter directly into path

Connector Development
1

Hi,
A quick question from me, I have an API that I’m building a connector for that defines the page size/number of rows returned by modifying the path.
i.e. /topstorageworkspaces/{limit}

Is there a way to inject this into path using the HttpRequester? I’ve had a look in the docs and cannot find anything for modifying the path like this, I can only find ways to add headers, parameters.

I’m currently using the following which worksm but I wonder if there is a better or more natural way to do this?

topstorageworkspaces_stream:
    $ref: "*ref(definitions.base_stream)"
    $options:
      name: "topstorageworkspaces"
      workspace_limit: 1000 # The number of workspaces returned, the max is 1000
      path: "/topstorageworkspaces/{{ options.workspace_limit }}"
2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Hey @will_m, thanks for your patience! That looks correct to me!