Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[request] Use Hasura API as a cron trigger webhook #5050

Open
jflambert opened this issue Jun 10, 2020 · 1 comment
Open

[request] Use Hasura API as a cron trigger webhook #5050

jflambert opened this issue Jun 10, 2020 · 1 comment
Assignees
Labels
a/eventing/cron-triggers c/scheduled-triggers k/ideas Discuss new ideas / pre-proposals / roadmap

Comments

@jflambert
Copy link
Contributor

jflambert commented Jun 10, 2020

The new 1.3.0 cron triggers feature has a "Webhooks" text box where users must input an endpoint and a payload. However the Hasura API is incompatible with the metadata included in cron triggers payloads (see #5438 for screenshots).

I think it would make sense to have a checkbox to enable external endpoints, but by default use the "local" hasura API endpoint. This way I could make administrative calls through run_sql (replacement for pgagent!) or automated remote schema registration.

@treystout
Copy link

I see that a spec has been merged to help support this feature (https://github.com/hasura/graphql-engine/blob/master/rfcs/transforms.md) what does this mean for this feature?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/eventing/cron-triggers c/scheduled-triggers k/ideas Discuss new ideas / pre-proposals / roadmap
Projects
None yet
Development

No branches or pull requests

5 participants