Hasura - v2.37.0

Changelog

Bug fixes and improvements

Server

• When adding a data connector agent, the agent URI can now be sourced from an environment variable (fix #9777).
• Allow ignoring the errors field if both data and errors are present in the Remote Schema response. Can be configured via the server HASURA_GRAPHQL_REMOTE_SCHEMA_PRIORITIZE_DATA env var or the remote-schema-prioritize-data flag.
• Remove additional internal error response field being returned in Async Actions when dev mode is false.
• Ensure Logical Models do not create empty GraphQL object types.
• Add a new environment variable HASURA_GRAPHQL_CONFIGURED_HEADER_PRECEDENCE to specify header precedence when delivering payload to webhook in actions and input validations.
• BigQuery filters now support ilike and nilike for case-insensitive versions of like and nlike.

Console

• Also prettify the query variables on hitting the GraphiQL Prettify button (fix #9968).
• Sort the columns in the filter and sort column selectors alphabetically in the data browser (fix #9966).
• Show table schema names in the new relationships UI for PostgreSQL and MS SQL Server.

Data Connectors

• Fix multi-schema issue for simple queries in Snowflake. (Cloud / Enterprise edition only)
• Fix aggregation limit for Snowflake, now aggregate limits are treated separately from row-based limits which can come through from permission-based limits. (Cloud / Enterprise edition only)
• Add support for the following additional JDBC auth mechanisms: (Cloud / Enterprise edition only)
• AWS
  • password managed by the AWS Secrets Manager
  • IAM based access for AWS (available for MySQL, MariaDB and PostgreSQL)
• Snowflake
  • encrypted private keys

Build

• Update the Ubuntu and Red Hat UBI base images to receive latest security updates