-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
server: add custom timeouts to actions #5762
Conversation
Deploy preview for hasura-docs ready! Built with commit c79e74e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
server LGTM
CHANGELOG.md
Outdated
@@ -56,6 +56,7 @@ This release contains the [PDV refactor (#4111)](https://github.com/hasura/graph | |||
- server: allow remote relationships joining `type` column with `[type]` input argument as spec allows this coercion (fixes #5133) | |||
- server: add action-like URL templating for event triggers and remote schemas (fixes #2483) | |||
- server: change `created_at` column type from `timestamp` to `timestamptz` for scheduled triggers tables (fix #5722) | |||
- server: allow adding custom timeouts to actions (fixes #4966) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
allow configuring timeouts for actions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
optional changelog comment
fixes #4966 #5673
Description
Changelog
CHANGELOG.md
is updated with user-facing content relevant to this PR. If no changelog is required, then add theno-changelog-required
label.Affected components
Related Issues
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
run_sql
auto manages the new metadata through schema diffing?run_sql
auto manages the definitions of metadata on renaming?export_metadata
/replace_metadata
supports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
query
types:args
payload which is not backward compatibleJSON
schemaGraphQL API
Schema Generation:
NamedType
Schema Resolve:-
null
value for any input fieldsLogging
JSON
schema has changedtype
names have changed