Is There a Workaround for Custom Response HTTP Request Trigger Issue during Development in GitHub?

1

This topic was automatically generated from Slack. You can find the original thread here.

I’ve noticed that when creating a Custom Response HTTP Request Trigger, with code step to return a custom response, that the API call will not return the custom response until that code is deployed or merged to your GitHub repository.

This complicates calling these webhooks from a parent workflow during development where there’s a PR process using the GitHub Sync integrations.

Is there a known work around to this that I’m missing (aside from passing data around with Data Stores or having a complicated PR & dev workflow)?

If not, I can put in a feature request for development versioning of webhook triggers and will work with my team to make decisions on how we want to proceed on data passing for now.

2

Yeah, lots of things are hard to test properly in development/before deployment. :disappointed:

Flow control is another one. It only works once deployed.

3

We usually find a way to work around it by making & testing more granular changes in a backward-compatible way, and then adapting the other workflows in a separate change/PR.

4

that’s well and good once you have an initial deployment of work in a project.

My proposed workarounds to my team at work is:

  1. Use a development workflow where sub-modules go through initial PR then use post-merge validations that the response data works with the parent workflows as intended.
  2. Switch up to passing data around using the Pipedream Data Stores (JSON schema NoSQL DB) until a feature is introduced to work with development versions of the API to clean up the development workflow process.

I’m leaning towards solution 2 since it simplifies the overall process, even if it adds additional code/steps to manage the data passing.

5

Yeah, both work. :+1:

We’re doing #1.

6

Well, I’m glad to hear that I’m not the only one that has encountered this issue, root caused it, and came up with a similar development workflow solution.

7

Same here! :smile:

8

Agree with both of you, thanks. This is already in our backlog but we created a ticket here in our public repo and would love some feedbacks from you guys

9

, thanks for the update. I’ve reviewed PipedreamHQ/pipedream#9231 and added a clarifying point about HTTP custom response bodies since this would be a powerful tool.