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

Cron trigger for mutations #9252

Open
karibertils opened this issue Nov 26, 2022 · 2 comments
Open

Cron trigger for mutations #9252

karibertils opened this issue Nov 26, 2022 · 2 comments
Labels
k/enhancement New feature or improve an existing feature t/gql-services

Comments

@karibertils
Copy link

Is your proposal related to a problem?

Sometimes I run into a scenario where I have an GraphQL mutation on a remote schema for an action that needs to be run periodically, as well as manually.

Describe the solution you'd like

Hasura could provide a way to create cron triggers which directly run mutations which are already available through Hasura. Normally these mutations only need static or no arguments.

Describe alternatives you've considered

An alternative is to create a web hook that calls the mutation and schedule that. Or create a web hook that does the same thing as the mutation. But this web hook would be unnecessary if Hasura could just schedule mutations directly.

@karibertils karibertils added the k/enhancement New feature or improve an existing feature label Nov 26, 2022
@rahulagarwal13
Copy link
Contributor

Hey @karibertils - thanks for proposing this solution. Agree this could be a useful enhancement but we do not have a timeline at present for it. Please keep following this Github issue for updates. Also would like to know more about your use of Actions and Remote Schemas in general, would you be interested to get on a brief call?

@zuohuadong
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k/enhancement New feature or improve an existing feature t/gql-services
Projects
None yet
Development

No branches or pull requests

4 participants