NOTE: 1.4 is now 2.0

Changelog

(Detailed changelog to be added soon)

Highlights

• Multiple Postgres Sources - You can now add multiple PG databases on the same Hasura instance

• Metadata storage separation - You can now store Hasura metadata in a separate (PG) database given by the env variable HASURA_GRAPHQL_METADATA_DATABASE_URL

• Volatile functions as mutations/queries - You can now track VOLATILE Postgres functions as mutations (or even queries)

• Remote Schema Permissions - You can now do role-based access control for remote schemas using field masking and argument presets. You need to enable this using HASURA_GRAPHQL_ENABLE_REMOTE_SCHEMA_PERMISSIONS: "true" env variable.

• REST Endpoint Support - You can now create REST endpoints on top of your GraphQL API. (Note: console support is pending)

• Heterogeneous Execution - You can now query Postgres databases and remote schema(s) in the same operation.

• CLI config v3 - To accomodate for multiple PG databases, the CLI project structure has been upgraded to v3. You can use the hasura scripts update-project-v3 command to upgrade your v2 project structure to v3. (You should keep a backup of the v2 project as the spec for the v3 config might change in future alpha versions)

  Support for CLI config v1 has been deprecated in this release. CLI config v2 will still be supported.

  Known bug: The CLI is not able to handle config v2 structured projects. This will be fixed in the next release.

  Note that as this release is still in alpha, a cli-migrations-v3 docker image to be used in CI/CD has not been released.

Note: This is an alpha release. Pls do not use this in production.

Using this release

Use the following docker image:

hasura/graphql-engine:v1.4.0-alpha.1