hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-16 01:44:03 +03:00
Code Issues Projects Releases Wiki Activity
fb3794c31a
graphql-engine/server/graphql-engine.cabal

399 lines
14 KiB
Plaintext
Raw Normal View History

move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
name: graphql-engine
version: 1.0.0
synopsis: GraphQL API over Postgres
-- description:
homepage: https://www.hasura.io
Changes license
2018-07-10 17:18:54 +03:00
license: AGPL-3.0
remove license file reference
2018-07-10 18:27:20 +03:00
-- license-file: LICENSE.md
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
author: Vamshi Surabhi
maintainer: vamshi@hasura.io
Changes license
2018-07-10 17:18:54 +03:00
copyright: 2017-2018 Hasura Techonologies Pvt. Ltd
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
category: Database
build-type: Simple
-- extra-source-files: README.md
cabal-version: >=1.10
source-repository head
type: git
location: https://github.com/hasura/graphql-engine
flag developer
description: operate in developer mode
default: False
manual: True
multiplexed subscriptions (#1934) * add types to represent unparsed http gql requests This will help when we add caching of frequently used ASTs * query plan caching * move livequery to execute * add multiplexed module * session variable can be customised depending on the context Previously the value was always "current_setting('hasura.user')" * get rid of typemap requirement in reusable plan * subscriptions are multiplexed when possible * use lazytx for introspection to avoid acquiring a pg connection * refactor to make execute a completely decoupled module * don't issue a transaction for a query * don't use current setting for explained sql * move postgres related types to a different module * validate variableValues on postgres before multiplexing subs * don't user current_setting for queries over ws * plan_cache is only visible when developer flag is enabled * introduce 'batch size' when multiplexing subscriptions * bump stackage to 13.16 * fix schema_stitching test case error code * store hashes instead of actual responses for subscriptions * internal api to dump subscriptions state * remove PlanCache from SchemaCacheRef * allow live query options to be configured on server startup * capture metrics for multiplexed subscriptions * more metrics captured for multiplexed subs * switch to tvar based hashmap for faster snapshotting * livequery modules do not expose internal details * fix typo in live query env vars * switch to hasura's pg-client-hs
2019-04-17 12:48:41 +03:00
flag profile
description: compile with profile options set
default: False
manual: True
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
library
hs-source-dirs: src-lib
basic test suite (#78) * server: basic test setup * server: use the default transaction mode * server: basic tests in yaml files * server: restructure test setup and some more tests
2018-07-11 10:13:07 +03:00
, src-exec
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
default-language: Haskell2010
build-depends: base
, pg-client
, text
explain a graphql query, similar to explain of an sql statement (close #562) (#805)
2018-10-19 05:15:28 +03:00
, text-builder >= 0.6
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, bytestring
, postgresql-libpq
, mtl
, aeson
, aeson-casing
, unordered-containers
, template-haskell
, hashable
, transformers
, transformers-base
, http-types
, attoparsec
server: use attoparsec-iso8601 for parsing time information
2018-06-28 10:11:49 +03:00
, attoparsec-iso8601 >= 1.0
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, time
, scientific
, Spock-core
, split
, optparse-applicative
, wai-extra
, containers
, monad-control
add support for jwt authorization (close #186) (#255) The API: 1. HGE has `--jwt-secret` flag or `HASURA_GRAPHQL_JWT_SECRET` env var. The value of which is a JSON. 2. The structure of this JSON is: `{"type": "<standard-JWT-algorithms>", "key": "<the-key>"}` `type` : Standard JWT algos : `HS256`, `RS256`, `RS512` etc. (see jwt.io). `key`: i. Incase of symmetric key, the key as it is. ii. Incase of asymmetric keys, only the public key, in a PEM encoded string or as a X509 certificate. 3. The claims in the JWT token must contain the following: i. `x-hasura-default-role` field: default role of that user ii. `x-hasura-allowed-roles` : A list of allowed roles for the user. The default role is overriden by `x-hasura-role` header. 4. The claims in the JWT token, can have other `x-hasura-*` fields where their values can only be strings. 5. The JWT tokens are sent as `Authorization: Bearer <token>` headers. --- To test: 1. Generate a shared secret (for HMAC-SHA256) or RSA key pair. 2. Goto https://jwt.io/ , add the keys 3. Edit the claims to have `x-hasura-role` (mandatory) and other `x-hasura-*` fields. Add permissions related to the claims to test permissions. 4. Start HGE with `--jwt-secret` flag or `HASURA_GRAPHQL_JWT_SECRET` env var, which takes a JSON string: `{"type": "HS256", "key": "mylongsharedsecret"}` or `{"type":"RS256", "key": "<PEM-encoded-public-key>"}` 5. Copy the JWT token from jwt.io and use it in the `Authorization: Bearer <token>` header. --- TODO: Support EC public keys. It is blocked on frasertweedale/hs-jose#61
2018-08-30 13:32:09 +03:00
, monad-time
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, wai-logger
, fast-logger
, wai
, postgresql-binary
server: add v1/version api, fix #34 (#37)
2018-07-03 18:34:25 +03:00
, process
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
-- Encoder related
, uuid
, vector
-- Logging related
, network
, byteorder
-- hashing for logging
, cryptonite
add support for jwt authorization (close #186) (#255) The API: 1. HGE has `--jwt-secret` flag or `HASURA_GRAPHQL_JWT_SECRET` env var. The value of which is a JSON. 2. The structure of this JSON is: `{"type": "<standard-JWT-algorithms>", "key": "<the-key>"}` `type` : Standard JWT algos : `HS256`, `RS256`, `RS512` etc. (see jwt.io). `key`: i. Incase of symmetric key, the key as it is. ii. Incase of asymmetric keys, only the public key, in a PEM encoded string or as a X509 certificate. 3. The claims in the JWT token must contain the following: i. `x-hasura-default-role` field: default role of that user ii. `x-hasura-allowed-roles` : A list of allowed roles for the user. The default role is overriden by `x-hasura-role` header. 4. The claims in the JWT token, can have other `x-hasura-*` fields where their values can only be strings. 5. The JWT tokens are sent as `Authorization: Bearer <token>` headers. --- To test: 1. Generate a shared secret (for HMAC-SHA256) or RSA key pair. 2. Goto https://jwt.io/ , add the keys 3. Edit the claims to have `x-hasura-role` (mandatory) and other `x-hasura-*` fields. Add permissions related to the claims to test permissions. 4. Start HGE with `--jwt-secret` flag or `HASURA_GRAPHQL_JWT_SECRET` env var, which takes a JSON string: `{"type": "HS256", "key": "mylongsharedsecret"}` or `{"type":"RS256", "key": "<PEM-encoded-public-key>"}` 5. Copy the JWT token from jwt.io and use it in the `Authorization: Bearer <token>` header. --- TODO: Support EC public keys. It is blocked on frasertweedale/hs-jose#61
2018-08-30 13:32:09 +03:00
-- for jwt verification
, jose
, pem
, x509
, asn1-encoding
, asn1-types
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
-- Server related
, warp
, th-lift-instances
, lens
-- GraphQL related
, graphql-parser
-- URL parser related
, network-uri
-- String related
, case-insensitive
, string-conversions
-- Http client
, wreq
, http-client
, http-client-tls
, connection
add event triggers (#329)
2018-09-05 14:26:46 +03:00
, retry
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
server: use insert-ordered-containers for ordered map
2018-06-28 11:19:27 +03:00
-- ordered map
, insert-ordered-containers
server: add v1/version api, fix #34 (#37)
2018-07-03 18:34:25 +03:00
-- Parsing SemVer
, semver
-- Templating
, mustache
add event triggers (#329)
2018-09-05 14:26:46 +03:00
, ginger
, file-embed
server: add v1/version api, fix #34 (#37)
2018-07-03 18:34:25 +03:00
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
--
, data-has
basic test suite (#78) * server: basic test setup * server: use the default transaction mode * server: basic tests in yaml files * server: restructure test setup and some more tests
2018-07-11 10:13:07 +03:00
-- for src-exec
, yaml
, template-haskell >= 2.11
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
initial support for livequeries (#176) fix #59
2018-07-20 10:22:46 +03:00
-- websockets interface related
, websockets
, wai-websockets
, hashtables
, stm
, stm-containers
, list-t
, async
-- logging related
, base64-bytestring >= 1.0
, auto-update
filter schema identifiers to conform to graphql naming scheme (close #134) (#211) * filter schema identifiers to conform to graphql naming scheme,closes #134 Filter out tables, columns, relationships etc which does not conform to graphql naming scheme. This ensures GraphiQL initialisation works properly for existing databases. * rename `isGraphQLConform` to `isValidName` * rename all graphQL validators
2018-07-27 12:50:12 +03:00
-- regex related
quote function and trigger names, allow hyphen in trigger name (#1012)
2018-11-13 08:58:55 +03:00
, regex-tdfa >= 1.2
filter schema identifiers to conform to graphql naming scheme (close #134) (#211) * filter schema identifiers to conform to graphql naming scheme,closes #134 Filter out tables, columns, relationships etc which does not conform to graphql naming scheme. This ensures GraphiQL initialisation works properly for existing databases. * rename `isGraphQLConform` to `isValidName` * rename all graphQL validators
2018-07-27 12:50:12 +03:00
refactor server cli code, add more cli options & version command (closes #51, #144, #1090, #1195) (#1200)
2018-12-14 06:21:41 +03:00
-- pretty printer
, ansi-wl-pprint
multiplexed subscriptions (#1934) * add types to represent unparsed http gql requests This will help when we add caching of frequently used ASTs * query plan caching * move livequery to execute * add multiplexed module * session variable can be customised depending on the context Previously the value was always "current_setting('hasura.user')" * get rid of typemap requirement in reusable plan * subscriptions are multiplexed when possible * use lazytx for introspection to avoid acquiring a pg connection * refactor to make execute a completely decoupled module * don't issue a transaction for a query * don't use current setting for explained sql * move postgres related types to a different module * validate variableValues on postgres before multiplexing subs * don't user current_setting for queries over ws * plan_cache is only visible when developer flag is enabled * introduce 'batch size' when multiplexing subscriptions * bump stackage to 13.16 * fix schema_stitching test case error code * store hashes instead of actual responses for subscriptions * internal api to dump subscriptions state * remove PlanCache from SchemaCacheRef * allow live query options to be configured on server startup * capture metrics for multiplexed subscriptions * more metrics captured for multiplexed subs * switch to tvar based hashmap for faster snapshotting * livequery modules do not expose internal details * fix typo in live query env vars * switch to hasura's pg-client-hs
2019-04-17 12:48:41 +03:00
-- metrics in multiplexed subs
, ekg-core
add name of ci environment to telemetry data (#2382)
2019-06-26 09:23:40 +03:00
-- metrics for CI integration
, ci-info
bundle console assets into server (close #516, close #521, close #2130) (#2192) This PR builds console static assets into the server docker image at `/srv/console-assets`. When env var `HASURA_GRAPHQL_CONSOLE_ASSETS_DIR=/srv/console-assets` or flag `--console-assets-dir=/srv/console-assets` is set on the server, the files in this directory are served at `/console/assets/*`. The console html template will have a variable called `cdnAssets: false` when this flag is set and it loads assets from server itself instead of CDN. The assets are moved to a new bucket with a new naming scheme: ``` graphql-engine-cdn.hasura.io/console/assets/ /common/{} /versioned/<version/{} /channel/<channel>/<version>/{} ``` Console served by CLI will still load assets from CDN - will fix that in the next release.
2019-05-16 10:45:29 +03:00
-- serve static files
, filepath >= 1.4
, mime-types >= 0.1
use bytestring builder to represent encoded json (#1800)
2019-03-18 19:22:21 +03:00
exposed-modules: Hasura.Prelude
, Hasura.Logging
, Hasura.EncJSON
multiplexed subscriptions (#1934) * add types to represent unparsed http gql requests This will help when we add caching of frequently used ASTs * query plan caching * move livequery to execute * add multiplexed module * session variable can be customised depending on the context Previously the value was always "current_setting('hasura.user')" * get rid of typemap requirement in reusable plan * subscriptions are multiplexed when possible * use lazytx for introspection to avoid acquiring a pg connection * refactor to make execute a completely decoupled module * don't issue a transaction for a query * don't use current setting for explained sql * move postgres related types to a different module * validate variableValues on postgres before multiplexing subs * don't user current_setting for queries over ws * plan_cache is only visible when developer flag is enabled * introduce 'batch size' when multiplexing subscriptions * bump stackage to 13.16 * fix schema_stitching test case error code * store hashes instead of actual responses for subscriptions * internal api to dump subscriptions state * remove PlanCache from SchemaCacheRef * allow live query options to be configured on server startup * capture metrics for multiplexed subscriptions * more metrics captured for multiplexed subs * switch to tvar based hashmap for faster snapshotting * livequery modules do not expose internal details * fix typo in live query env vars * switch to hasura's pg-client-hs
2019-04-17 12:48:41 +03:00
, Hasura.Db
, Hasura.Cache
use bytestring builder to represent encoded json (#1800)
2019-03-18 19:22:21 +03:00
, Hasura.Server.App
initial support for livequeries (#176) fix #59
2018-07-20 10:22:46 +03:00
, Hasura.Server.Auth
add support for jwt authorization (close #186) (#255) The API: 1. HGE has `--jwt-secret` flag or `HASURA_GRAPHQL_JWT_SECRET` env var. The value of which is a JSON. 2. The structure of this JSON is: `{"type": "<standard-JWT-algorithms>", "key": "<the-key>"}` `type` : Standard JWT algos : `HS256`, `RS256`, `RS512` etc. (see jwt.io). `key`: i. Incase of symmetric key, the key as it is. ii. Incase of asymmetric keys, only the public key, in a PEM encoded string or as a X509 certificate. 3. The claims in the JWT token must contain the following: i. `x-hasura-default-role` field: default role of that user ii. `x-hasura-allowed-roles` : A list of allowed roles for the user. The default role is overriden by `x-hasura-role` header. 4. The claims in the JWT token, can have other `x-hasura-*` fields where their values can only be strings. 5. The JWT tokens are sent as `Authorization: Bearer <token>` headers. --- To test: 1. Generate a shared secret (for HMAC-SHA256) or RSA key pair. 2. Goto https://jwt.io/ , add the keys 3. Edit the claims to have `x-hasura-role` (mandatory) and other `x-hasura-*` fields. Add permissions related to the claims to test permissions. 4. Start HGE with `--jwt-secret` flag or `HASURA_GRAPHQL_JWT_SECRET` env var, which takes a JSON string: `{"type": "HS256", "key": "mylongsharedsecret"}` or `{"type":"RS256", "key": "<PEM-encoded-public-key>"}` 5. Copy the JWT token from jwt.io and use it in the `Authorization: Bearer <token>` header. --- TODO: Support EC public keys. It is blocked on frasertweedale/hs-jose#61
2018-08-30 13:32:09 +03:00
, Hasura.Server.Auth.JWT
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.Server.Init
forward set-cookie headers from remote servers (fix #1654) (#2305)
2019-06-04 13:10:28 +03:00
, Hasura.Server.Context
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.Server.Middleware
, Hasura.Server.Logging
, Hasura.Server.Query
, Hasura.Server.Utils
add support for multiple domains in cors config (close #1436) (#1536) Support for multiple domains (as CSV) in the `--cors-domain` flag and `HASURA_GRAPHQL_CORS_DOMAIN` env var. Following are all valid configurations (must include scheme and optional port): ```shell HASURA_GRAPHQL_CORS_DOMAIN="https://*.foo.bar.com:8080" HASURA_GRAPHQL_CORS_DOMAIN="https://*.foo.bar.com, http://*.localhost, https://example.com" HASURA_GRAPHQL_CORS_DOMAIN="*" HASURA_GRAPHQL_CORS_DOMAIN="http://example.com, http://*.localhost, http://localhost:3000, https://*.foo.bar.com, https://foo.bar.com" ``` **Note**: top-level domains are not considered as part of wildcard domains. You have to add them separately. E.g - `https://*.foo.com` doesn't include `https://foo.com`. The default (if the flag or env var is not specified) is `*`. Which means CORS headers are sent for all domains.
2019-02-14 08:58:38 +03:00
, Hasura.Server.Cors
server: add v1/version api, fix #34 (#37)
2018-07-03 18:34:25 +03:00
, Hasura.Server.Version
check for updates every 24 hrs in background (fix #204) (#209)
2018-07-27 12:34:50 +03:00
, Hasura.Server.CheckUpdates
add anonymous telemetry (#1401)
2019-01-28 16:55:28 +03:00
, Hasura.Server.Telemetry
sync metadata cache across multiple instances connected to same db (closes #1182) (#1574) 1. Haskel library `pg-client-hs` has been updated to expose a function that helps listen to `postgres` notifications over a `channel` in this [PR](https://github.com/hasura/pg-client-hs/pull/5) 2. The server records an event in a table `hdb_catalog.hdb_cache_update_event` whenever any `/v1/query` (that changes metadata) is requested. A trigger notifies a `cache update` event via `hasura_cache_update` channel 3. The server runs two concurrent threads namely `listener` and `processor`. The `listener` thread listens to events on `hasura_cache_update` channel and pushed into a `Queue`. The `processor` thread fetches events from that `Queue` and processes it. Thus server rebuilds schema cache from database and updates.
2019-03-12 08:46:27 +03:00
, Hasura.Server.SchemaUpdate
add an api to dump postgres schema (close #1939) (#1967)
2019-04-30 11:34:08 +03:00
, Hasura.Server.PGDump
add api to get server config details (close #1831); add jwt-analyzer (close #1369) (#1925)
2019-06-11 16:29:03 +03:00
, Hasura.Server.Config
bundle console assets into server (close #516, close #521, close #2130) (#2192) This PR builds console static assets into the server docker image at `/srv/console-assets`. When env var `HASURA_GRAPHQL_CONSOLE_ASSETS_DIR=/srv/console-assets` or flag `--console-assets-dir=/srv/console-assets` is set on the server, the files in this directory are served at `/console/assets/*`. The console html template will have a variable called `cdnAssets: false` when this flag is set and it loads assets from server itself instead of CDN. The assets are moved to a new bucket with a new naming scheme: ``` graphql-engine-cdn.hasura.io/console/assets/ /common/{} /versioned/<version/{} /channel/<channel>/<version>/{} ``` Console served by CLI will still load assets from CDN - will fix that in the next release.
2019-05-16 10:45:29 +03:00
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.Types
, Hasura.RQL.Instances
adds basic support for remote schemas/schema stitching (#952)
2018-11-23 16:02:46 +03:00
, Hasura.RQL.Types.SchemaCache
, Hasura.RQL.Types.SchemaCacheTypes
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.Types.Common
optimise server startup time (close #1430) (#2120) 1. Reuses postgres connections during startup which reduces the overhead of opening and closing connections. 2. Faster schema cache building. This is done by fetching all the required data in a single sql statement.
2019-05-08 10:36:43 +03:00
, Hasura.RQL.Types.Catalog
fix sql generation for boolean expressions, closes #853 (#1037) When using self referential relationships in boolean expressions, the exists clause incorrectly uses the table names to qualify columns which will be the same for parent table and the child table. This is now fixed by generating unique aliases as we traverse down the relationships.
2018-11-16 15:40:23 +03:00
, Hasura.RQL.Types.BoolExp
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.Types.Permission
, Hasura.RQL.Types.Error
, Hasura.RQL.Types.DML
breaking: drop id from event_triggers table (fix #1840) (#1857)
2019-03-25 20:10:52 +03:00
, Hasura.RQL.Types.EventTrigger
adds basic support for remote schemas/schema stitching (#952)
2018-11-23 16:02:46 +03:00
, Hasura.RQL.Types.RemoteSchema
recover from inconsistent database state (closes #231) (#1863)
2019-04-17 19:29:39 +03:00
, Hasura.RQL.Types.Metadata
support allow-list for graphql queries (closes #989) (#2075)
2019-05-16 09:13:25 +03:00
, Hasura.RQL.Types.QueryCollection
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.DDL.Deps
, Hasura.RQL.DDL.Permission.Internal
fix upsert queries to work on non admin roles (fix #239) (#291)
2018-08-17 17:44:43 +03:00
, Hasura.RQL.DDL.Permission.Triggers
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.DDL.Permission
, Hasura.RQL.DDL.Relationship
allow renaming tables, columns and relationships (close #79) (#1542)
2019-03-01 12:17:22 +03:00
, Hasura.RQL.DDL.Relationship.Rename
, Hasura.RQL.DDL.Relationship.Types
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.DDL.QueryTemplate
, Hasura.RQL.DDL.Schema.Table
allow renaming tables, columns and relationships (close #79) (#1542)
2019-03-01 12:17:22 +03:00
, Hasura.RQL.DDL.Schema.Rename
allow exposing postgres functions through GraphQL interface (close #333) (#1073)
2019-01-25 06:31:54 +03:00
, Hasura.RQL.DDL.Schema.Function
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.DDL.Schema.Diff
, Hasura.RQL.DDL.Metadata
, Hasura.RQL.DDL.Utils
breaking: drop id from event_triggers table (fix #1840) (#1857)
2019-03-25 20:10:52 +03:00
, Hasura.RQL.DDL.EventTrigger
adds basic support for remote schemas/schema stitching (#952)
2018-11-23 16:02:46 +03:00
, Hasura.RQL.DDL.Headers
, Hasura.RQL.DDL.RemoteSchema
support allow-list for graphql queries (closes #989) (#2075)
2019-05-16 09:13:25 +03:00
, Hasura.RQL.DDL.QueryCollection
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.DML.Delete
, Hasura.RQL.DML.Internal
, Hasura.RQL.DML.Insert
fix mutation returning when relationships are present (fix #1576) (#1703) If returning field contains nested selections then mutation is performed in two steps 1. Mutation is performed with returning columns of any primary key and unique constraints 2. returning fields are queried on rows returned by selecting from table by filtering with column values returned in Step 1. Since mutation takes two courses based on selecting relations in returning field, it is hard to maintain sequence of prepared arguments (PrepArg) generated while resolving returning field. So, we're using txtConverter instead of prepare to resolve mutation fields.
2019-03-07 13:24:07 +03:00
, Hasura.RQL.DML.Mutation
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.DML.Returning
refactor select query generation (#941)
2018-10-31 15:51:20 +03:00
, Hasura.RQL.DML.Select.Internal
allow ordering with aggregated fields (close #1039) (#1042)
2018-12-12 15:58:39 +03:00
, Hasura.RQL.DML.Select.Types
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.DML.Select
, Hasura.RQL.DML.Update
, Hasura.RQL.DML.Count
, Hasura.RQL.DML.QueryTemplate
, Hasura.RQL.GBoolExp
initial support for livequeries (#176) fix #59
2018-07-20 10:22:46 +03:00
, Hasura.GraphQL.Transport.HTTP.Protocol
, Hasura.GraphQL.Transport.HTTP
, Hasura.GraphQL.Transport.WebSocket.Protocol
, Hasura.GraphQL.Transport.WebSocket.Server
, Hasura.GraphQL.Transport.WebSocket
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.GraphQL.Schema
, Hasura.GraphQL.Utils
initial support for livequeries (#176) fix #59
2018-07-20 10:22:46 +03:00
, Hasura.GraphQL.Validate
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.GraphQL.Validate.Types
, Hasura.GraphQL.Validate.Context
, Hasura.GraphQL.Validate.Field
, Hasura.GraphQL.Validate.InputValue
explain a graphql query, similar to explain of an sql statement (close #562) (#805)
2018-10-19 05:15:28 +03:00
, Hasura.GraphQL.Explain
refactor graphql query execution logic (#1855)
2019-03-25 21:25:25 +03:00
, Hasura.GraphQL.Execute
multiplexed subscriptions (#1934) * add types to represent unparsed http gql requests This will help when we add caching of frequently used ASTs * query plan caching * move livequery to execute * add multiplexed module * session variable can be customised depending on the context Previously the value was always "current_setting('hasura.user')" * get rid of typemap requirement in reusable plan * subscriptions are multiplexed when possible * use lazytx for introspection to avoid acquiring a pg connection * refactor to make execute a completely decoupled module * don't issue a transaction for a query * don't use current setting for explained sql * move postgres related types to a different module * validate variableValues on postgres before multiplexing subs * don't user current_setting for queries over ws * plan_cache is only visible when developer flag is enabled * introduce 'batch size' when multiplexing subscriptions * bump stackage to 13.16 * fix schema_stitching test case error code * store hashes instead of actual responses for subscriptions * internal api to dump subscriptions state * remove PlanCache from SchemaCacheRef * allow live query options to be configured on server startup * capture metrics for multiplexed subscriptions * more metrics captured for multiplexed subs * switch to tvar based hashmap for faster snapshotting * livequery modules do not expose internal details * fix typo in live query env vars * switch to hasura's pg-client-hs
2019-04-17 12:48:41 +03:00
, Hasura.GraphQL.Execute.Plan
, Hasura.GraphQL.Execute.Query
, Hasura.GraphQL.Execute.LiveQuery
, Hasura.GraphQL.Execute.LiveQuery.Types
, Hasura.GraphQL.Execute.LiveQuery.Multiplexed
, Hasura.GraphQL.Execute.LiveQuery.Fallback
refactor graphql query execution logic (#1855)
2019-03-25 21:25:25 +03:00
, Hasura.GraphQL.Resolve
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.GraphQL.Resolve.BoolExp
, Hasura.GraphQL.Resolve.Context
, Hasura.GraphQL.Resolve.InputValue
, Hasura.GraphQL.Resolve.Introspect
insert mutations can now handle nested-data/relationsips (close #343) (#429)
2018-10-05 18:13:51 +03:00
, Hasura.GraphQL.Resolve.Insert
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.GraphQL.Resolve.Mutation
, Hasura.GraphQL.Resolve.Select
adds basic support for remote schemas/schema stitching (#952)
2018-11-23 16:02:46 +03:00
, Hasura.GraphQL.RemoteServer
, Hasura.GraphQL.Context
, Hasura.GraphQL.Resolve.ContextTypes
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
add event triggers (#329)
2018-09-05 14:26:46 +03:00
, Hasura.Events.Lib
, Hasura.Events.HTTP
refactor to remove warnings especially with orphan instances (#1163) * remove phase one/two distinction and hdbquery typeclass * move extensions to default-extensions * switch to LazyTx which only acquires a connection if needed * move defns from TH module into Ops module * remove tojson orphan instance for http exception * remove orphan instance for dmlp1 * getTopLevelNodes will not throw any exceptions
2018-12-13 10:26:15 +03:00
, Hasura.HTTP
adds basic support for remote schemas/schema stitching (#952)
2018-11-23 16:02:46 +03:00
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Data.Text.Extended
multiplexed subscriptions (#1934) * add types to represent unparsed http gql requests This will help when we add caching of frequently used ASTs * query plan caching * move livequery to execute * add multiplexed module * session variable can be customised depending on the context Previously the value was always "current_setting('hasura.user')" * get rid of typemap requirement in reusable plan * subscriptions are multiplexed when possible * use lazytx for introspection to avoid acquiring a pg connection * refactor to make execute a completely decoupled module * don't issue a transaction for a query * don't use current setting for explained sql * move postgres related types to a different module * validate variableValues on postgres before multiplexing subs * don't user current_setting for queries over ws * plan_cache is only visible when developer flag is enabled * introduce 'batch size' when multiplexing subscriptions * bump stackage to 13.16 * fix schema_stitching test case error code * store hashes instead of actual responses for subscriptions * internal api to dump subscriptions state * remove PlanCache from SchemaCacheRef * allow live query options to be configured on server startup * capture metrics for multiplexed subscriptions * more metrics captured for multiplexed subs * switch to tvar based hashmap for faster snapshotting * livequery modules do not expose internal details * fix typo in live query env vars * switch to hasura's pg-client-hs
2019-04-17 12:48:41 +03:00
, Data.Aeson.Extended
server: use insert-ordered-containers for ordered map
2018-06-28 11:19:27 +03:00
, Data.Sequence.NonEmpty
initial support for livequeries (#176) fix #59
2018-07-20 10:22:46 +03:00
, Data.TByteString
server: use insert-ordered-containers for ordered map
2018-06-28 11:19:27 +03:00
, Data.HashMap.Strict.InsOrd.Extended
add a json path argument to query values inside json columns (close #1598) (#1661)
2019-03-25 16:45:35 +03:00
, Data.Parser.JSONPath
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.SQL.DML
, Hasura.SQL.Types
, Hasura.SQL.Value
, Hasura.SQL.GeoJSON
, Hasura.SQL.Time
workaround postgres default limit of 63 chars for identifiers (close #688) (#707)
2018-10-12 12:28:43 +03:00
, Hasura.SQL.Rewrite
adds basic support for remote schemas/schema stitching (#952)
2018-11-23 16:02:46 +03:00
, Network.URI.Extended
basic test suite (#78) * server: basic test setup * server: use the default transaction mode * server: basic tests in yaml files * server: restructure test setup and some more tests
2018-07-11 10:13:07 +03:00
, Ops
allow renaming tables, columns and relationships (close #79) (#1542)
2019-03-01 12:17:22 +03:00
, Migrate
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
jwt config now takes a jwk url (close #465) (#527) JWT config now takes an optional jwk_url parameter (which points to published JWK Set). This is useful for providers who rotate their JWK Set. Optional jwk_url parameter is taken. The published JWK set under that URL should be in standard JWK format (tools.ietf.org/html/rfc7517#section-4.8). If the response contains an Expires header, the JWK set is automatically refreshed.
2018-09-27 14:22:49 +03:00
other-modules: Hasura.Server.Auth.JWT.Internal
, Hasura.Server.Auth.JWT.Logging
refactor to remove warnings especially with orphan instances (#1163) * remove phase one/two distinction and hdbquery typeclass * move extensions to default-extensions * switch to LazyTx which only acquires a connection if needed * move defns from TH module into Ops module * remove tojson orphan instance for http exception * remove orphan instance for dmlp1 * getTopLevelNodes will not throw any exceptions
2018-12-13 10:26:15 +03:00
default-extensions: EmptyCase
FlexibleContexts
FlexibleInstances
InstanceSigs
MultiParamTypeClasses
LambdaCase
MultiWayIf
TupleSections
DeriveFoldable
DeriveFunctor
DeriveGeneric
DeriveLift
DeriveTraversable
GeneralizedNewtypeDeriving
BangPatterns
OverloadedStrings
ScopedTypeVariables
TemplateHaskell
QuasiQuotes
TypeFamilies
NoImplicitPrelude
jwt config now takes a jwk url (close #465) (#527) JWT config now takes an optional jwk_url parameter (which points to published JWK Set). This is useful for providers who rotate their JWK Set. Optional jwk_url parameter is taken. The published JWK set under that URL should be in standard JWK format (tools.ietf.org/html/rfc7517#section-4.8). If the response contains an Expires header, the JWK set is automatically refreshed.
2018-09-27 14:22:49 +03:00
multiplexed subscriptions (#1934) * add types to represent unparsed http gql requests This will help when we add caching of frequently used ASTs * query plan caching * move livequery to execute * add multiplexed module * session variable can be customised depending on the context Previously the value was always "current_setting('hasura.user')" * get rid of typemap requirement in reusable plan * subscriptions are multiplexed when possible * use lazytx for introspection to avoid acquiring a pg connection * refactor to make execute a completely decoupled module * don't issue a transaction for a query * don't use current setting for explained sql * move postgres related types to a different module * validate variableValues on postgres before multiplexing subs * don't user current_setting for queries over ws * plan_cache is only visible when developer flag is enabled * introduce 'batch size' when multiplexing subscriptions * bump stackage to 13.16 * fix schema_stitching test case error code * store hashes instead of actual responses for subscriptions * internal api to dump subscriptions state * remove PlanCache from SchemaCacheRef * allow live query options to be configured on server startup * capture metrics for multiplexed subscriptions * more metrics captured for multiplexed subs * switch to tvar based hashmap for faster snapshotting * livequery modules do not expose internal details * fix typo in live query env vars * switch to hasura's pg-client-hs
2019-04-17 12:48:41 +03:00
if flag(profile)
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
ghc-prof-options: -rtsopts -fprof-auto -fno-prof-count-entries
multiplexed subscriptions (#1934) * add types to represent unparsed http gql requests This will help when we add caching of frequently used ASTs * query plan caching * move livequery to execute * add multiplexed module * session variable can be customised depending on the context Previously the value was always "current_setting('hasura.user')" * get rid of typemap requirement in reusable plan * subscriptions are multiplexed when possible * use lazytx for introspection to avoid acquiring a pg connection * refactor to make execute a completely decoupled module * don't issue a transaction for a query * don't use current setting for explained sql * move postgres related types to a different module * validate variableValues on postgres before multiplexing subs * don't user current_setting for queries over ws * plan_cache is only visible when developer flag is enabled * introduce 'batch size' when multiplexing subscriptions * bump stackage to 13.16 * fix schema_stitching test case error code * store hashes instead of actual responses for subscriptions * internal api to dump subscriptions state * remove PlanCache from SchemaCacheRef * allow live query options to be configured on server startup * capture metrics for multiplexed subscriptions * more metrics captured for multiplexed subs * switch to tvar based hashmap for faster snapshotting * livequery modules do not expose internal details * fix typo in live query env vars * switch to hasura's pg-client-hs
2019-04-17 12:48:41 +03:00
if flag(developer)
bundle console assets into server (close #516, close #521, close #2130) (#2192) This PR builds console static assets into the server docker image at `/srv/console-assets`. When env var `HASURA_GRAPHQL_CONSOLE_ASSETS_DIR=/srv/console-assets` or flag `--console-assets-dir=/srv/console-assets` is set on the server, the files in this directory are served at `/console/assets/*`. The console html template will have a variable called `cdnAssets: false` when this flag is set and it loads assets from server itself instead of CDN. The assets are moved to a new bucket with a new naming scheme: ``` graphql-engine-cdn.hasura.io/console/assets/ /common/{} /versioned/<version/{} /channel/<channel>/<version>/{} ``` Console served by CLI will still load assets from CDN - will fix that in the next release.
2019-05-16 10:45:29 +03:00
cpp-options: -DDeveloperAPIs
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
refactor to remove warnings especially with orphan instances (#1163) * remove phase one/two distinction and hdbquery typeclass * move extensions to default-extensions * switch to LazyTx which only acquires a connection if needed * move defns from TH module into Ops module * remove tojson orphan instance for http exception * remove orphan instance for dmlp1 * getTopLevelNodes will not throw any exceptions
2018-12-13 10:26:15 +03:00
ghc-options: -O2
-Wall
-Wcompat
-Wincomplete-record-updates
-Wincomplete-uni-patterns
-Wredundant-constraints
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
executable graphql-engine
refactor to remove warnings especially with orphan instances (#1163) * remove phase one/two distinction and hdbquery typeclass * move extensions to default-extensions * switch to LazyTx which only acquires a connection if needed * move defns from TH module into Ops module * remove tojson orphan instance for http exception * remove orphan instance for dmlp1 * getTopLevelNodes will not throw any exceptions
2018-12-13 10:26:15 +03:00
default-extensions: EmptyCase
FlexibleContexts
FlexibleInstances
InstanceSigs
MultiParamTypeClasses
LambdaCase
MultiWayIf
TupleSections
DeriveFoldable
DeriveFunctor
DeriveGeneric
DeriveLift
DeriveTraversable
GeneralizedNewtypeDeriving
BangPatterns
OverloadedStrings
ScopedTypeVariables
TemplateHaskell
QuasiQuotes
TypeFamilies
NoImplicitPrelude
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
main-is: Main.hs
default-language: Haskell2010
hs-source-dirs: src-exec
build-depends: base
initial support for livequeries (#176) fix #59
2018-07-20 10:22:46 +03:00
, warp >= 3.2
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, graphql-engine
, aeson >= 1.0
, bytestring >= 0.10
, mtl
, optparse-applicative >= 0.12
, yaml
basic test suite (#78) * server: basic test setup * server: use the default transaction mode * server: basic tests in yaml files * server: restructure test setup and some more tests
2018-07-11 10:13:07 +03:00
, template-haskell >= 2.11 , time >= 1.6
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, text
, lens
, unordered-containers >= 0.2
, pg-client
check for updates every 24 hrs in background (fix #204) (#209)
2018-07-27 12:34:50 +03:00
, http-client
, http-client-tls
add event triggers (#329)
2018-09-05 14:26:46 +03:00
, stm
, wreq
, connection
jwt config now takes a jwk url (close #465) (#527) JWT config now takes an optional jwk_url parameter (which points to published JWK Set). This is useful for providers who rotate their JWK Set. Optional jwk_url parameter is taken. The published JWK set under that URL should be in standard JWK format (tools.ietf.org/html/rfc7517#section-4.8). If the response contains an Expires header, the JWK set is automatically refreshed.
2018-09-27 14:22:49 +03:00
, string-conversions
sync metadata cache across multiple instances connected to same db (closes #1182) (#1574) 1. Haskel library `pg-client-hs` has been updated to expose a function that helps listen to `postgres` notifications over a `channel` in this [PR](https://github.com/hasura/pg-client-hs/pull/5) 2. The server records an event in a table `hdb_catalog.hdb_cache_update_event` whenever any `/v1/query` (that changes metadata) is requested. A trigger notifies a `cache update` event via `hasura_cache_update` channel 3. The server runs two concurrent threads namely `listener` and `processor`. The `listener` thread listens to events on `hasura_cache_update` channel and pushed into a `Queue`. The `processor` thread fetches events from that `Queue` and processes it. Thus server rebuilds schema cache from database and updates.
2019-03-12 08:46:27 +03:00
, uuid
check for updates every 24 hrs in background (fix #204) (#209)
2018-07-27 12:34:50 +03:00
allow renaming tables, columns and relationships (close #79) (#1542)
2019-03-01 12:17:22 +03:00
other-modules: Ops
, Migrate
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
if flag(developer)
ghc-prof-options: -rtsopts -fprof-auto -fno-prof-count-entries
link server with -rtsopts (#2233) This allows customisation of Haskell's runtime system's parameters.
2019-05-21 12:28:08 +03:00
ghc-options: -O2
-Wall
-Wcompat
-Wincomplete-record-updates
-Wincomplete-uni-patterns
-Wredundant-constraints
-threaded -rtsopts
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
basic test suite (#78) * server: basic test setup * server: use the default transaction mode * server: basic tests in yaml files * server: restructure test setup and some more tests
2018-07-11 10:13:07 +03:00
test-suite graphql-engine-test
type: exitcode-stdio-1.0
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
main-is: Main.hs
Default-Language: Haskell2010
Hs-Source-Dirs: test
ghc-options: -O2 -Wall
Build-Depends: Spock-core >= 0.11
, base
basic test suite (#78) * server: basic test setup * server: use the default transaction mode * server: basic tests in yaml files * server: restructure test setup and some more tests
2018-07-11 10:13:07 +03:00
, aeson
, aeson-casing
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, bytestring
, hspec
, hspec-core
, hspec-wai
, optparse-applicative
, graphql-engine -any
, text
, wai
, pg-client
basic test suite (#78) * server: basic test setup * server: use the default transaction mode * server: basic tests in yaml files * server: restructure test setup and some more tests
2018-07-11 10:13:07 +03:00
, time
, yaml
check for updates every 24 hrs in background (fix #204) (#209)
2018-07-27 12:34:50 +03:00
, http-client
, http-client-tls
better error code when insertion check constraint fails (fix #257) (#267)
2018-08-10 15:05:07 +03:00
, unordered-containers >= 0.2
, case-insensitive
basic test suite (#78) * server: basic test setup * server: use the default transaction mode * server: basic tests in yaml files * server: restructure test setup and some more tests
2018-07-11 10:13:07 +03:00
add event triggers (#329)
2018-09-05 14:26:46 +03:00
other-modules: Spec
Reference in New Issue Copy Permalink