v2.13.0
·
4677 commits
to master
since this release
Changelog
Auto cleanup for event triggers
(Enterprise edition only)
You can now configure automatic clean up of event triggers logs with various configuration parameters. Read more about it here
Source health checks
(Enterprise edition only)
Introducing health checks for data sources. Health check on a source can be enabled and configurable via an optional health_check field in the source metadata.
Example for a Postgres source.
POST /v1/metadata HTTP/1.1
Content-Type: application/json
X-Hasura-Role: admin
{
"type":"pg_add_source",
"args":{
"name":"<db_name>",
"configuration":{
"connection_info":{
"database_url":{
"from_env":"<DATABASE_URL_ENV>"
}
}
},
"health_check": {
"test": {
"sql": "SELECT 1"
},
"interval": 300,
"timeout": 5,
"retries": 3,
"retry_interval": 5
}
}
}Please refer to our docs for more information.
Reporting source health check
(Enterprise edition only)
Health check reports of sources can be obtained through a GET request from the /healthz/sources, an admin-only endpoint, on demand. Learn more about the API here.
Currently, Hasura supports enabling health checks on Postgres and MS SQL Server databases. Support for other data sources will be added soon.
Bug fixes and improvements
- server: Strings in suitable notation are now permitted for all numerical input fields.
- server: Fix bug that didn't stream any data when the cursor column of a streaming subscription had a custom identifier set.
- server: fix handling non-latin text elements in array literals in Postgres (fix #8961)
- server: Make
argsoptional in BigQuery computed fields that are backed by functions that don't take any user-specified arguments. (close #8904) - server: Fix an issue the server's handling of the
graphql-wsprotocol, in which the server can cause an infinite ping-pong loop. (fix #8967) - server: Add
get_rows_countarg inget_event_invocationsandget_scheduled_eventsmetadata APIs, when it isfalse, the total rows count is not included in the response. - server: drop associated event triggers when a source is removed via the
replace_metadatametadata API - server: update tracing log to use original hex values sent in request header
- server: Improve error reporting when root fields originating from Actions or Remote schemas conflict
- server: fix applying migrations when the same SQL function is used as both a computed field and as a root field (fix #8643)
- server: Support 128-bit trace ids (Enterprise edition only)
- console: fix local object relationship deletion in new relationships page (fix #9024)
- console: Add a shortcut for creating a query collection operation using the introspection query or any query defined in the GraphiQL tab
- console: add schema preview for remote schemas
- console: Remove the old allow list section and add a link to the new Allow List Manager in the settings.
- console: Fix column selection bug for select and insert permissions on the table permissions page (fix #8937)
- console: allow users to edit comments on DB views using the console (fix #8846)
- console: allow resizing GraphiQL in API explorer (fix #8880)
- cli: Fix
schemablock being dropped from SDL when exporting remote schema permissions (fix #8579)