Changelog
This is the 4th alpha release for v2.0.0. The biggest highlight of this release is Inherited Roles. There are other fixes and improvements mainly for MSSQL data source.
Inherited Roles
You can now create an Inherited Role which allows you to combine multiple roles into one role (in an additive way). This solves fundamental problems with permission system (as described in #877 and #3442) and also helps you manage roles in a modular way.
To get started, head to Hasura Console, Settings -> Inherited Roles (read docs here)
In the first version, only Postgres queries and subscriptions are exposed for an inherited role.
PS: Inherited roles is currently an experimental feature. To enable inherited roles, start the Hasura server with environment variable HASURA_GRAPHQL_EXPERIMENTAL_FEATURES: "inherited_roles"
CLI
If your upgrading from a previous alpha, be aware that there are some subtle changes in the organisation of the metadata directory. So, once you update the server please do a hasura metadata export. This should make sure your project is up to date with the latest changes.
Bug fixes and improvements
- server/mssql: support tracking and querying from views
- server: fix issue when a remote relationship's joining field had a custom GraphQL name defined (fix #6626)
- server: fix handling of nullable object relationships (fix #6633)
- console: add inherited roles support
- console: add permissions support for mssql tables
- cli: support rest endpoints
- cli: support mssql sources
- cli: use relative paths in metadata !include directives
- cli: rename
--databaseflag inmigrateandseedcommand to--database-name - cli: support inherited roles
Using this release
Use the following docker image:
hasura/graphql-engine:v2.0.0-alpha.4