You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
jflambert
changed the title
[request] Set current Hasura instance as a cron trigger webhook
[request] Use Hasura API as a cron trigger webhook
Jul 28, 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.The text was updated successfully, but these errors were encountered: