Changelog

2019-05-16 17:45 IST: The fixed image has been pushed with tag v1.0.0-beta.1
2019-05-16 15:53 IST: (We have taken the docker images down from docker hub as there seem to be some issue serving console html - will post an update soon)

A new v1/graphql endpoint 🎉

This release introduces a new endpoint, /v1/graphql, that will be the primary GraphQL endpoint going forward. Breaking changes in this release (described below) have been released only into this endpoint, leaving the /v1alpha1/graphql endpoint unaffected by them.

New Features & enhancements 🎁

• Allow-list: A list of safe queries can now be configured in GraphQL engine. When enabled, it is used to restrict GraphQL engine so that it executes only those queries that are present in the list. See docs for more details. This is enforced over both v1 and v1alpha1 GraphQL endpoints. (closes #989) (#2075)

• Optimised server startup time: Startup time for GraphQL engine has been reduced by ~7X to ~30X depending on the quantum of metadata (startup time is ~0.26 secs with 300 tables and 1300 relationships). (closes #1430) (#2120)

• Manual Event triggers: Events can now be configured to be triggered manually using the console. Read more here. (closes #1687) (#2077)

• Console features: The console now has native support for creating/deleting the following Postgres elements:

  • Multi-column unique constraints (closes #506) (#2148)
  • Schemas (closes #2142) (#2143)

• Offline mode for console: GraphQL engine's console now works without access to a public network. The console's static assets are bundled into the Docker image, and GraphQL engine can be configured to use locally available static files instead of relying on a CDN. This feature is currently not available for a console instance served by the CLI, this will be addressed in the next releases. See docs for
  more information. (closes #516, #521, #2130) (#2192, #2201)

Breaking change in v1/graphql 🔨

The following changes are available only in the v1/graphql endpoint and are breaking only when compared to the behaviour of the v1alpha1/graphql endpoint:

• Response codes: All graphql responses in the /v1/graphql endpoint will be 200 OK. Most GraphQL clients expect responses to be HTTP 200 to parse the error properly. Non-200 responses are considered transport layer errors.

• Consistent error messages: Errors in HTTP and Websocket layer are now consistent and have the same structure. (closes #1368) (#2064) (#2173)

Bug Fixes 🐞

• Websocket connections will now be closed automatically on JWT expiry. (fixes #578) (#2156)
• Fixed sending duplicate content-type headers to remote schemas. (fixes #2159) (#2170) (#2197)
• Boolean Environment variables will be compared with a case-insensitive match. (fixes #2177) (#2182)

Other changes

• Fixes and enhancements for https://learn.hasura.io. (closes #2161) (#2158, #2166, #2162, #2136, #2169, #2134, #2091, #2154)
• Console bug fixes. (closes #2164, #1777, #2094) (#2187, #2152, #2127, #2123)
• Community content & docs changes. (#2157, #2145, #2149, #1963, #2110, #2126, #2196, #2150)