How to Trigger and Debug the `deploy` Function after Deploying a Broken Source Code using the CLI?

Help
1

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

If I’ve got code I want to test in a source’s deploy function, how can I trigger it again after deploying it with the cli? I basically just want to debug that function since it seems like the Discourse new-posts-added source is broken. Using it in a workflow as a trigger shows no events when testing nor does it load the initial events pulled by the call to the Discord REST API. But when using the CLI to deploy it works fine.

2

No matter what there’s a bug in categories configuration. It says to “leave blank to watch all categories” but the drop down forces you to choose at least one.

3

The deploy function runs once once, and doesn’t run anytime again in a source’s lifecycle. That’s different from the activate and deactivate functions

4

Do you see anything in the source’s logs?

5

Yeah, I was hoping there was a better way to test code in deploy than to have to redeploy every time.

6

I’m adding debug statements.

7

There’s an error trying to delete the webhook on Discourse

8

but that doesn’t seem to affect the deploy issue

9

No matter what there’s a bug in categories configuration. It says to “leave blank to watch all categories” but the drop down forces you to choose at least one.
Yeah that’s strange, the prop should be optional

10

I get the latest posts as events on deploy… but it’s using the REST API to do that… I think the webhooks aren’t being generated properly.

11

Hmm got it

12

The deploy function will usually use the API to fetch historical events

13

the webhook calls are reverse engineered so there’s probably an issue there… or with permissions in discord

14

And then after it’s deployed, it should create a webhook in Discourse and start receiving new events through taht

15

Yeah, that deploy pull works fine when run with pd dev

16

but used as a trigger it does nothing.

17

Have you double checked the permissions for your API Key?

18

Yeah, but I’ll do it again just in case lol

19

We use that trigger internally and for some automations

20

it’s all users and global scope