hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-10-05 06:18:04 +03:00
Code Issues Projects Releases Wiki Activity
2735d284c1
graphql-engine/server/graphql-engine.cabal

463 lines
17 KiB
Plaintext
Raw Normal View History

save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
cabal-version: 2.2
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
homepage: https://www.hasura.io
update server cabal file to reflect the correct license (#2471)
2019-07-04 13:58:02 +03:00
license: Apache-2.0
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
author: Vamshi Surabhi
maintainer: vamshi@hasura.io
update server cabal file to reflect the correct license (#2471)
2019-07-04 13:58:02 +03:00
copyright: Hasura Inc.
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
category: Database
build-type: Simple
source-repository head
type: git
location: https://github.com/hasura/graphql-engine
flag developer
Switch from `stack` to `cabal-install` for building server code (close #3280) (#3558) Co-authored-by: Alexis King <lexi.lambda@gmail.com>
2020-01-18 01:07:15 +03:00
description: Enable support for development-only APIs
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
default: False
manual: True
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
common common-all
ghc-options:
Switch from `stack` to `cabal-install` for building server code (close #3280) (#3558) Co-authored-by: Alexis King <lexi.lambda@gmail.com>
2020-01-18 01:07:15 +03:00
-fmax-simplifier-iterations=20 -foptimal-applicative-do
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
-Wall -Wcompat -Wincomplete-record-updates -Wincomplete-uni-patterns -Wredundant-constraints
if flag(developer)
cpp-options: -DDeveloperAPIs
default-language: Haskell2010
default-extensions:
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
ApplicativeDo BangPatterns BlockArguments ConstraintKinds DefaultSignatures DeriveDataTypeable
DeriveFoldable DeriveFunctor DeriveGeneric DeriveLift DeriveTraversable DerivingVia EmptyCase
FlexibleContexts FlexibleInstances FunctionalDependencies GeneralizedNewtypeDeriving
InstanceSigs LambdaCase MultiParamTypeClasses MultiWayIf NamedFieldPuns NoImplicitPrelude
OverloadedStrings QuantifiedConstraints QuasiQuotes RankNTypes ScopedTypeVariables
StandaloneDeriving TemplateHaskell TupleSections TypeApplications TypeFamilies TypeOperators
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
common common-exe
ghc-options:
-threaded -rtsopts
-- Re. `-I2` see #2565
incremental metadata: Clean up a few lingering loose ends - Move MonadBase/MonadBaseControl instances for TxE into pg-client-hs - Set the -qn2 RTS option by default to limit the parallel GC to 2 threads - Remove eventlog instrumentation - Don’t rebuild the schema cache again after running a query that needs it to be rebuilt, since we do that explicitly now. - Remove some redundant checks, and relocate a couple others.
2020-01-09 02:19:02 +03:00
--
-- `-qn2` limits the parallel GC to at most 2 capabilities. This came up in #3354/#3394, as the
-- parallel GC was causing significant performance overhead. Folks in #ghc on freenode advised
-- limiting the parallel GC to 2 or 3 capabilities as a very conservative choice, since more
-- than that is highly unlikely to ever be helpful. More benchmarking would be useful to know if
-- this is the right decision. It’s possible it would better to just turn it off completely.
"-with-rtsopts=-N -I2 -qn2"
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
library
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
import: common-all
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
hs-source-dirs: src-lib
build-depends: base
fix resolving user info in websocket transport (#3509) The connection handler in websocket transport was not using the 'UserAuthentication' interface to resolve user info. Fix resolving user info in websocket transport to use the common 'UserAuthentication' interface
2019-12-11 04:04:49 +03:00
, lifted-base
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, 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
, 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
Add support for GraphQL enum types via enum table references These changes also add a new type, PGColumnType, between PGColInfo and PGScalarType, and they process PGRawColumnType values into PGColumnType values during schema cache generation.
2019-07-22 15:47:13 +03:00
, monad-validate
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, fast-logger
, wai
, postgresql-binary
server: add v1/version api, fix #34 (#37)
2018-07-03 18:34:25 +03:00
, process
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
, http-client-tls
Add Hasura.Incremental, a library for incremental builds
2019-11-18 21:45:54 +03:00
, profunctors
Use arrows instead of monads to define the schema cache construction
2019-11-27 01:49:42 +03:00
, deepseq
Add support for fine-grained dependency tracking to Incremental
2019-12-15 16:28:23 +03:00
, dependent-map >=0.2.4 && <0.4
, dependent-sum >=0.4 && <0.5
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
-- `these >=1` is split into several different packages, but our current stack
-- resolver has `these <1`; when we upgrade we just need to add an extra
-- dependency on `semialign`
Use arrows instead of monads to define the schema cache construction
2019-11-27 01:49:42 +03:00
, these >=0.7.1 && <0.8
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
-- Encoder related
, uuid
, vector
-- Logging related
, network
, byteorder
breaking: server logging changes (close #507, close #2171) (#1835)
2019-07-11 08:37:06 +03:00
-- for parsing RSA keys
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, cryptonite
breaking: server logging changes (close #507, close #2171) (#1835)
2019-07-11 08:37:06 +03:00
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
server: Parameterize the graphql-engine library over the version (#3668)
2020-01-23 00:55:55 +03:00
, uri-encode
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
-- String related
, case-insensitive
support intersect filters on raster columns (close #2613) (#2704) * initial raster support * _st_intersects_geom -> _st_intersects_geom_nband * add tests * update docs * improve docs As requested by @marionschleifer * new type for raster values Suggested by @lexi-lambda * replace `SEUnsafe "NULL"` with SENull
2019-08-29 16:07:05 +03:00
, text-conversions
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
-- Http client
, wreq
, http-client
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
, file-embed
Make catalog metadata migrations work on all schema versions (fix #2826) (#2379) * Separate DB and metadata migrations * Refactor Migrate.hs to generate list of migrations at compile-time * Replace ginger with shakespeare to improve performance * Improve migration log messages
2019-10-11 08:13:57 +03:00
, shakespeare >= 2.0.22
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
, stm
, stm-containers
, list-t
, async
fix resolving user info in websocket transport (#3509) The connection handler in websocket transport was not using the 'UserAuthentication' interface to resolve user info. Fix resolving user info in websocket transport to use the common 'UserAuthentication' interface
2019-12-11 04:04:49 +03:00
, lifted-async
More robust forking, exception safety. Closes #3768 (#3860) This is the result of a general audit of how we fork threads, with a detour into how we're using mutable state especially in websocket codepaths, making more robust to async exceptions and exceptions resulting from bugs. Some highlights: - use a wrapper around 'immortal' so threads that die due to bugs are restarted, and log the error - use 'withAsync' some places - use bracket a few places where we might break invariants - log some codepaths that represent bugs - export UnstructuredLog for ad hoc logging (the alternative is we continue not logging useful stuff) I had to timebox this. There are a few TODOs I didn't want to address. And we'll wait until this is merged to attempt #3705 for Control.Concurrent.Extended
2020-03-05 20:59:26 +03:00
, immortal < 0.3
initial support for livequeries (#176) fix #59
2018-07-20 10:22:46 +03:00
-- 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
server: prevent metadata checks in read-only mode (#4250) * do not perform the metadata check in read-only mode * improve the isAltrDropReplace regex * quote the regex at compile-time to handle syntax errors statically Co-authored-by: Alexis King <lexi.lambda@gmail.com>
2020-04-02 02:22:55 +03:00
, regex-tdfa >=1.3.1 && <1.4
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
allow fetching gc stats through dev api (#2489)
2019-07-10 15:01:52 +03:00
-- for capturing various metrics
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
, ekg-core
allow fetching gc stats through dev api (#2489)
2019-07-10 15:01:52 +03:00
, ekg-json
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
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
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
-- for handling posix signals for graceful shutdown
, unix
add gzip brotli compression to http responses (close #2674) (#2751)
2019-09-19 15:54:40 +03:00
-- HTTP compression
, zlib
allow specifying an upper limit on the query plan cache size (#3012)
2019-11-25 20:12:23 +03:00
-- caching
, psqueues >= 0.2
export metadata without nulls, empty arrays & default values (#3393) * export metadata without nulls, empty arrays * property tests for 'ReplaceMetadata' using QuickCheck -> Derive Arbitrary class for 'ReplaceMetadata' dependant types * reduce property test cases number to 30 QuickCheck generates the `ReplaceMetadata` value really large for higher number test cases. Encoded JSON for such values is large and consumes more memory. Thus, CI is giving up while running property tests. * circle-ci: Add property tests as saperate job * add no command mode to tests * add yaml.v2 to go mod * remove indirect comment for yaml.v2 dependency
2019-12-14 09:47:38 +03:00
-- testing
, QuickCheck
, generic-arbitrary
server: prevent metadata checks in read-only mode (#4250) * do not perform the metadata check in read-only mode * improve the isAltrDropReplace regex * quote the regex at compile-time to handle syntax errors statically Co-authored-by: Alexis King <lexi.lambda@gmail.com>
2020-04-02 02:22:55 +03:00
-- 0.6.1 is supposedly not okay for ghc 8.6:
-- https://github.com/nomeata/ghc-heap-view/issues/27
Use AssertNF for leak prophylaxis when doing mutable writes. Closes #3937 (#4097) Writing to a mutable var is a particularly potent source of leaks since it mostly defeats GHC's analysis. Here we add assertions to all mutable writes, and fix a couple spots where we wrote some thunks to a mutable var (compiled with -O2). Some of these thunks were probably benign, but others looked liked they might be retaining big args. Didn't do much analysis, just fixed. Actually pretty happy with how easy this was to use and as a diagnostic, once I sorted out some issues. We should consider using it elsewhere, and maybe extending so that we can use it with tests, enable when `-fenable-assertsions` etc. Relates #3388 Also simplified codepaths that use `AcceptWith`, which has unnecessary `Maybe` fields.
2020-03-18 04:31:22 +03:00
, ghc-heap-view == 0.6.0
server: prevent metadata checks in read-only mode (#4250) * do not perform the metadata check in read-only mode * improve the isAltrDropReplace regex * quote the regex at compile-time to handle syntax errors statically Co-authored-by: Alexis King <lexi.lambda@gmail.com>
2020-04-02 02:22:55 +03:00
Add downgrade command (close #1156) (#3760) * Add downgrade command * Add docs per @lexi-lambda's suggestions * make tests pass * Update hdb_version once, from Haskell * more work based on feedback * Improve the usage message * Small docs changes * Test downgrades exist for each tag * Update downgrading.rst * Use git-log to find tags which are ancestors of the current commit Co-authored-by: Vamshi Surabhi <0x777@users.noreply.github.com>
2020-02-07 14:03:12 +03:00
, directory
export metadata without nulls, empty arrays & default values (#3393) * export metadata without nulls, empty arrays * property tests for 'ReplaceMetadata' using QuickCheck -> Derive Arbitrary class for 'ReplaceMetadata' dependant types * reduce property test cases number to 30 QuickCheck generates the `ReplaceMetadata` value really large for higher number test cases. Encoded JSON for such values is large and consumes more memory. Thus, CI is giving up while running property tests. * circle-ci: Add property tests as saperate job * add no command mode to tests * add yaml.v2 to go mod * remove indirect comment for yaml.v2 dependency
2019-12-14 09:47:38 +03:00
Use arrows instead of monads to define the schema cache construction
2019-11-27 01:49:42 +03:00
exposed-modules: Control.Arrow.Extended
Move arrow transformers into a separate module
2019-12-14 13:38:44 +03:00
, Control.Arrow.Trans
Use arrows instead of monads to define the schema cache construction
2019-11-27 01:49:42 +03:00
, Control.Monad.Stateless
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
, Control.Monad.Unique
Add request timings and count histograms to telemetry. Closes #3552 We upload a set of accumulating timers and counters to track service time for different types of operations, across several dimensions (e.g. did we hit the plan cache, was a remote involved, etc.) Also... Standardize on DiffTime as a standard duration type, and try to use it consistently. See discussion here: https://github.com/hasura/graphql-engine/pull/3584#pullrequestreview-340679369 It should be possible to overwrite that module so the new threadDelay sticks per the pattern in #3705 blocked on #3558 Rename the Control.Concurrent.Extended.threadDelay to `sleep` since a naive use with a literal argument would be very bad! We catch a bug in 'computeTimeDiff'. Add convenient 'Read' instances to the time unit utility types. Make 'Second' a newtype to support this.
2020-01-16 04:56:57 +03:00
, Data.Time.Clock.Units
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
fix cache-control header parsing for JWK (fix #3655) (#3676) write a proper parser according to the RFC https://tools.ietf.org/html/rfc7234#section-5.2
2020-01-14 00:56:51 +03:00
-- exposed for tests
, Data.Parser.CacheControl
allow custom mutations through actions (#3042) * basic doc for actions * custom_types, sync and async actions * switch to graphql-parser-hs on github * update docs * metadata import/export * webhook calls are now supported * relationships in sync actions * initialise.sql is now in sync with the migration file * fix metadata tests * allow specifying arguments of actions * fix blacklist check on check_build_worthiness job * track custom_types and actions related tables * handlers are now triggered on async actions * default to pgjson unless a field is involved in relationships, for generating definition list * use 'true' for action filter for non admin role * fix create_action_permission sql query * drop permissions when dropping an action * add a hdb_role view (and relationships) to fetch all roles in the system * rename 'webhook' key in action definition to 'handler' * allow templating actions wehook URLs with env vars * add 'update_action' /v1/query type * allow forwarding client headers by setting `forward_client_headers` in action definition * add 'headers' configuration in action definition * handle webhook error response based on status codes * support array relationships for custom types * implement single row mutation, see https://github.com/hasura/graphql-engine/issues/3731 * single row mutation: rename 'pk_columns' -> 'columns' and no-op refactor * use top level primary key inputs for delete_by_pk & account select permissions for single row mutations * use only REST semantics to resolve the webhook response * use 'pk_columns' instead of 'columns' for update_by_pk input * add python basic tests for single row mutations * add action context (name) in webhook payload * Async action response is accessible for non admin roles only if the request session vars equals to action's * clean nulls, empty arrays for actions, custom types in export metadata * async action mutation returns only the UUID of the action * unit tests for URL template parser * Basic sync actions python tests * fix output in async query & add async tests * add admin secret header in async actions python test * document async action architecture in Resolve/Action.hs file * support actions returning array of objects * tests for list type response actions * update docs with actions and custom types metadata API reference * update actions python tests as per #f8e1330 Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com> Co-authored-by: Aravind Shankar <face11301@gmail.com> Co-authored-by: Rakesh Emmadi <12475069+rakeshkky@users.noreply.github.com>
2020-02-13 20:38:23 +03:00
, Data.URL.Template
fix cache-control header parsing for JWK (fix #3655) (#3676) write a proper parser according to the RFC https://tools.ietf.org/html/rfc7234#section-5.2
2020-01-14 00:56:51 +03:00
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
, Hasura.Prelude
, Hasura.App
, Hasura.Db
Initial benchmarks for caching. Closes #3530 These aren't suitable e.g. for running in CI since some take far too long (and an impossibly long-time when running under criterion's normal bootstrapping sampling regime. We might try to improve this ourselves: https://github.com/bos/criterion/issues/218 An initial summary analysis will be in #3530.
2019-12-13 22:52:19 +03:00
-- Exposed for benchmark:
server: avoid code duplication using type classes (#4624) There are two implementations of a Cache, namely a bounded and an unbounded variant. This can be elegantly captured in a type class. In addition to reducing the amount of error-prone code in the definition of the cache, this version reduces the amount of error-prone code in usage sites of the cache, as it makes the cache into an abstract object, so that a calling site cannot distinguish between cache types. Any decision about what should be cached should be made through the interface of a cache, rather than at the callsite, and this is captured by this variant.
2020-05-13 12:17:32 +03:00
, Hasura.Cache.Types
Initial benchmarks for caching. Closes #3530 These aren't suitable e.g. for running in CI since some take far too long (and an impossibly long-time when running under criterion's normal bootstrapping sampling regime. We might try to improve this ourselves: https://github.com/bos/criterion/issues/218 An initial summary analysis will be in #3530.
2019-12-13 22:52:19 +03:00
, Hasura.Cache.Bounded
, Hasura.Cache.Unbounded
, Hasura.Cache
use bytestring builder to represent encoded json (#1800)
2019-03-18 19:22:21 +03:00
, Hasura.Logging
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
, Hasura.HTTP
Add Hasura.Incremental, a library for incremental builds
2019-11-18 21:45:54 +03:00
, Hasura.Incremental
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
, Hasura.Server.App
, Hasura.Server.Auth
, Hasura.Server.Init
improve debug information in actions errors response (close #4031) (#4432) * config options for internal errors for non-admin role, close #4031 More detailed action debug info is added in response 'internal' field * add docs * update CHANGELOG.md * set admin graphql errors option in ci tests, minor changes to docs * fix tests Don't use any auth for sync actions error tests. The request body changes based on auth type in session_variables (x-hasura-auth-mode) * Apply suggestions from code review Co-Authored-By: Marion Schleifer <marion@hasura.io> * use a new sum type to represent the inclusion of internal errors As suggested in review by @0x777 -> Move around few modules in to specific API folder -> Saperate types from Init.hs * fix tests Don't use any auth for sync actions error tests. The request body changes based on auth type in session_variables (x-hasura-auth-mode) * move 'HttpResponse' to 'Hasura.HTTP' module * update change log with breaking change warning * Update CHANGELOG.md Co-authored-by: Marion Schleifer <marion@hasura.io> Co-authored-by: Tirumarai Selvan <tiru@hasura.io>
2020-04-24 10:55:51 +03:00
, Hasura.Server.Init.Config
, Hasura.Server.API.Query
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
, Hasura.Server.Utils
, Hasura.Server.Version
, Hasura.Server.Logging
, Hasura.Server.Migrate
, Hasura.Server.Compression
improve debug information in actions errors response (close #4031) (#4432) * config options for internal errors for non-admin role, close #4031 More detailed action debug info is added in response 'internal' field * add docs * update CHANGELOG.md * set admin graphql errors option in ci tests, minor changes to docs * fix tests Don't use any auth for sync actions error tests. The request body changes based on auth type in session_variables (x-hasura-auth-mode) * Apply suggestions from code review Co-Authored-By: Marion Schleifer <marion@hasura.io> * use a new sum type to represent the inclusion of internal errors As suggested in review by @0x777 -> Move around few modules in to specific API folder -> Saperate types from Init.hs * fix tests Don't use any auth for sync actions error tests. The request body changes based on auth type in session_variables (x-hasura-auth-mode) * move 'HttpResponse' to 'Hasura.HTTP' module * update change log with breaking change warning * Update CHANGELOG.md Co-authored-by: Marion Schleifer <marion@hasura.io> Co-authored-by: Tirumarai Selvan <tiru@hasura.io>
2020-04-24 10:55:51 +03:00
, Hasura.Server.API.PGDump
Add request timings and count histograms to telemetry. Closes #3552 We upload a set of accumulating timers and counters to track service time for different types of operations, across several dimensions (e.g. did we hit the plan cache, was a remote involved, etc.) Also... Standardize on DiffTime as a standard duration type, and try to use it consistently. See discussion here: https://github.com/hasura/graphql-engine/pull/3584#pullrequestreview-340679369 It should be possible to overwrite that module so the new threadDelay sticks per the pattern in #3705 blocked on #3558 Rename the Control.Concurrent.Extended.threadDelay to `sleep` since a naive use with a literal argument would be very bad! We catch a bug in 'computeTimeDiff'. Add convenient 'Read' instances to the time unit utility types. Make 'Second' a newtype to support this.
2020-01-16 04:56:57 +03:00
-- Exposed for testing:
, Hasura.Server.Telemetry.Counters
accept a new argument `claims_namespace_path` in JWT config (#4365) * add new optional field `claims_namespace_path` in JWT config * return value when empty array is found in executeJSONPath * update the docs related to claims_namespace_path * improve encodeJSONPath, add property tests for parseJSONPath * throw error if both claims_namespace_path and claims_namespace are set * refactor the Data.Parser.JsonPath to Data.Parser.JSONPathSpec * update the JWT docs Co-Authored-By: Marion Schleifer <marion@hasura.io> Co-authored-by: Marion Schleifer <marion@hasura.io> Co-authored-by: rakeshkky <12475069+rakeshkky@users.noreply.github.com> Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com>
2020-04-16 09:45:21 +03:00
, Data.Parser.JSONPath
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
, Hasura.RQL.Types
Split up Hasura.RQL.DDL.Schema.Cache This should hopefully improve compile times by avoiding the need to specialize everything at once.
2019-12-09 01:17:39 +03:00
, Hasura.RQL.Types.Run
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
, Hasura.RQL.DDL.Metadata
export metadata without nulls, empty arrays & default values (#3393) * export metadata without nulls, empty arrays * property tests for 'ReplaceMetadata' using QuickCheck -> Derive Arbitrary class for 'ReplaceMetadata' dependant types * reduce property test cases number to 30 QuickCheck generates the `ReplaceMetadata` value really large for higher number test cases. Encoded JSON for such values is large and consumes more memory. Thus, CI is giving up while running property tests. * circle-ci: Add property tests as saperate job * add no command mode to tests * add yaml.v2 to go mod * remove indirect comment for yaml.v2 dependency
2019-12-14 09:47:38 +03:00
, Hasura.RQL.DDL.Metadata.Types
, Hasura.RQL.DDL.Metadata.Generator
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
, Hasura.RQL.DDL.Schema
use bytestring builder to represent encoded json (#1800)
2019-03-18 19:22:21 +03:00
, Hasura.EncJSON
backend only insert permissions (rfc #4120) (#4224) * move user info related code to Hasura.User module * the RFC #4120 implementation; insert permissions with admin secret * revert back to old RoleName based schema maps An attempt made to avoid duplication of schema contexts in types if any role doesn't possess any admin secret specific schema * fix compile errors in haskell test * keep 'user_vars' for session variables in http-logs * no-op refacto * tests for admin only inserts * update docs for admin only inserts * updated CHANGELOG.md * default behaviour when admin secret is not set * fix x-hasura-role to X-Hasura-Role in pytests * introduce effective timeout in actions async tests * update docs for admin-secret not configured case * Update docs/graphql/manual/api-reference/schema-metadata-api/permission.rst Co-Authored-By: Marion Schleifer <marion@hasura.io> * Apply suggestions from code review Co-Authored-By: Marion Schleifer <marion@hasura.io> * a complete iteration backend insert permissions accessable via 'x-hasura-backend-privilege' session variable * console changes for backend-only permissions * provide tooltip id; update labels and tooltips; * requested changes * requested changes - remove className from Toggle component - use appropriate function name (capitalizeFirstChar -> capitalize) * use toggle props from definitelyTyped * fix accidental commit * Revert "introduce effective timeout in actions async tests" This reverts commit b7a59c19d643520cfde6af579889e1038038438a. * generate complete schema for both 'default' and 'backend' sessions * Apply suggestions from code review Co-Authored-By: Marion Schleifer <marion@hasura.io> * remove unnecessary import, export Toggle as is * update session variable in tooltip * 'x-hasura-use-backend-only-permissions' variable to switch * update help texts * update docs * update docs * update console help text * regenerate package-lock * serve no backend schema when backend_only: false and header set to true - Few type name refactor as suggested by @0x777 * update CHANGELOG.md * Update CHANGELOG.md * Update CHANGELOG.md * fix a merge bug where a certain entity didn't get removed Co-authored-by: Marion Schleifer <marion@hasura.io> Co-authored-by: Rishichandra Wawhal <rishi@hasura.io> Co-authored-by: rikinsk <rikin.kachhia@gmail.com> Co-authored-by: Tirumarai Selvan <tiru@hasura.io>
2020-04-24 12:10:53 +03:00
, Hasura.Session
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
export metadata without nulls, empty arrays & default values (#3393) * export metadata without nulls, empty arrays * property tests for 'ReplaceMetadata' using QuickCheck -> Derive Arbitrary class for 'ReplaceMetadata' dependant types * reduce property test cases number to 30 QuickCheck generates the `ReplaceMetadata` value really large for higher number test cases. Encoded JSON for such values is large and consumes more memory. Thus, CI is giving up while running property tests. * circle-ci: Add property tests as saperate job * add no command mode to tests * add yaml.v2 to go mod * remove indirect comment for yaml.v2 dependency
2019-12-14 09:47:38 +03:00
, Data.Aeson.Ordered
Add support for fine-grained dependency tracking to Incremental
2019-12-15 16:28:23 +03:00
other-modules: Hasura.Incremental.Select
, Hasura.Incremental.Internal.Cache
, Hasura.Incremental.Internal.Dependency
, Hasura.Incremental.Internal.Rule
, Hasura.Server.Auth.JWT
server: add support for webhook connection expiration (#4196) * add expiry time to webhook user info This also adds an optional message to webhook errors: if we fail to parse an expiry time, we will log a warning with the parse error. * refactored Auth This change had one main goal: put in common all expiry time extraction code between the JWT and WebHook parts of the code. Furthermore, this change also moves all WebHook specific code to its own module, similarly to what is done for JWT. * Remove dependency on string-conversions in favor of text-conversions string-conversions silently uses UTF8 instead of being explicit about it, and it uses lenientDecode when decoding ByteStrings when it’s usually better to reject invalid UTF8 input outright. text-conversions solves both those problems. Co-authored-by: Alexis King <lexi.lambda@gmail.com>
2020-04-03 03:00:13 +03:00
, Hasura.Server.Auth.WebHook
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.Server.Middleware
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
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
improve debug information in actions errors response (close #4031) (#4432) * config options for internal errors for non-admin role, close #4031 More detailed action debug info is added in response 'internal' field * add docs * update CHANGELOG.md * set admin graphql errors option in ci tests, minor changes to docs * fix tests Don't use any auth for sync actions error tests. The request body changes based on auth type in session_variables (x-hasura-auth-mode) * Apply suggestions from code review Co-Authored-By: Marion Schleifer <marion@hasura.io> * use a new sum type to represent the inclusion of internal errors As suggested in review by @0x777 -> Move around few modules in to specific API folder -> Saperate types from Init.hs * fix tests Don't use any auth for sync actions error tests. The request body changes based on auth type in session_variables (x-hasura-auth-mode) * move 'HttpResponse' to 'Hasura.HTTP' module * update change log with breaking change warning * Update CHANGELOG.md Co-authored-by: Marion Schleifer <marion@hasura.io> Co-authored-by: Tirumarai Selvan <tiru@hasura.io>
2020-04-24 10:55:51 +03:00
, Hasura.Server.API.Config
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
, Hasura.Server.Migrate.Version
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
, Hasura.Server.Auth.JWT.Internal
, Hasura.Server.Auth.JWT.Logging
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.Instances
adds basic support for remote schemas/schema stitching (#952)
2018-11-23 16:02:46 +03:00
, Hasura.RQL.Types.SchemaCache
allow custom mutations through actions (#3042) * basic doc for actions * custom_types, sync and async actions * switch to graphql-parser-hs on github * update docs * metadata import/export * webhook calls are now supported * relationships in sync actions * initialise.sql is now in sync with the migration file * fix metadata tests * allow specifying arguments of actions * fix blacklist check on check_build_worthiness job * track custom_types and actions related tables * handlers are now triggered on async actions * default to pgjson unless a field is involved in relationships, for generating definition list * use 'true' for action filter for non admin role * fix create_action_permission sql query * drop permissions when dropping an action * add a hdb_role view (and relationships) to fetch all roles in the system * rename 'webhook' key in action definition to 'handler' * allow templating actions wehook URLs with env vars * add 'update_action' /v1/query type * allow forwarding client headers by setting `forward_client_headers` in action definition * add 'headers' configuration in action definition * handle webhook error response based on status codes * support array relationships for custom types * implement single row mutation, see https://github.com/hasura/graphql-engine/issues/3731 * single row mutation: rename 'pk_columns' -> 'columns' and no-op refactor * use top level primary key inputs for delete_by_pk & account select permissions for single row mutations * use only REST semantics to resolve the webhook response * use 'pk_columns' instead of 'columns' for update_by_pk input * add python basic tests for single row mutations * add action context (name) in webhook payload * Async action response is accessible for non admin roles only if the request session vars equals to action's * clean nulls, empty arrays for actions, custom types in export metadata * async action mutation returns only the UUID of the action * unit tests for URL template parser * Basic sync actions python tests * fix output in async query & add async tests * add admin secret header in async actions python test * document async action architecture in Resolve/Action.hs file * support actions returning array of objects * tests for list type response actions * update docs with actions and custom types metadata API reference * update actions python tests as per #f8e1330 Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com> Co-authored-by: Aravind Shankar <face11301@gmail.com> Co-authored-by: Rakesh Emmadi <12475069+rakeshkky@users.noreply.github.com>
2020-02-13 20:38:23 +03:00
, Hasura.RQL.Types.Table
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
, Hasura.RQL.Types.SchemaCache.Build
adds basic support for remote schemas/schema stitching (#952)
2018-11-23 16:02:46 +03:00
, Hasura.RQL.Types.SchemaCacheTypes
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
functions can access session info via input arg (close #2322) (#3143)
2019-11-20 09:47:06 +03:00
, Hasura.RQL.Types.Function
Add support for GraphQL enum types via enum table references These changes also add a new type, PGColumnType, between PGColInfo and PGScalarType, and they process PGRawColumnType values into PGColumnType values during schema cache generation.
2019-07-22 15:47:13 +03:00
, Hasura.RQL.Types.Catalog
, Hasura.RQL.Types.Column
, Hasura.RQL.Types.Common
support computed fields returning scalars or set of tables (close #1387) (#2917)
2019-10-18 11:29:47 +03:00
, Hasura.RQL.Types.ComputedField
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.Types.DML
Add support for GraphQL enum types via enum table references These changes also add a new type, PGColumnType, between PGColInfo and PGScalarType, and they process PGRawColumnType values into PGColumnType values during schema cache generation.
2019-07-22 15:47:13 +03:00
, Hasura.RQL.Types.Error
breaking: drop id from event_triggers table (fix #1840) (#1857)
2019-03-25 20:10:52 +03:00
, Hasura.RQL.Types.EventTrigger
recover from inconsistent database state (closes #231) (#1863)
2019-04-17 19:29:39 +03:00
, Hasura.RQL.Types.Metadata
Add support for GraphQL enum types via enum table references These changes also add a new type, PGColumnType, between PGColInfo and PGScalarType, and they process PGRawColumnType values into PGColumnType values during schema cache generation.
2019-07-22 15:47:13 +03:00
, Hasura.RQL.Types.Permission
support allow-list for graphql queries (closes #989) (#2075)
2019-05-16 09:13:25 +03:00
, Hasura.RQL.Types.QueryCollection
allow custom mutations through actions (#3042) * basic doc for actions * custom_types, sync and async actions * switch to graphql-parser-hs on github * update docs * metadata import/export * webhook calls are now supported * relationships in sync actions * initialise.sql is now in sync with the migration file * fix metadata tests * allow specifying arguments of actions * fix blacklist check on check_build_worthiness job * track custom_types and actions related tables * handlers are now triggered on async actions * default to pgjson unless a field is involved in relationships, for generating definition list * use 'true' for action filter for non admin role * fix create_action_permission sql query * drop permissions when dropping an action * add a hdb_role view (and relationships) to fetch all roles in the system * rename 'webhook' key in action definition to 'handler' * allow templating actions wehook URLs with env vars * add 'update_action' /v1/query type * allow forwarding client headers by setting `forward_client_headers` in action definition * add 'headers' configuration in action definition * handle webhook error response based on status codes * support array relationships for custom types * implement single row mutation, see https://github.com/hasura/graphql-engine/issues/3731 * single row mutation: rename 'pk_columns' -> 'columns' and no-op refactor * use top level primary key inputs for delete_by_pk & account select permissions for single row mutations * use only REST semantics to resolve the webhook response * use 'pk_columns' instead of 'columns' for update_by_pk input * add python basic tests for single row mutations * add action context (name) in webhook payload * Async action response is accessible for non admin roles only if the request session vars equals to action's * clean nulls, empty arrays for actions, custom types in export metadata * async action mutation returns only the UUID of the action * unit tests for URL template parser * Basic sync actions python tests * fix output in async query & add async tests * add admin secret header in async actions python test * document async action architecture in Resolve/Action.hs file * support actions returning array of objects * tests for list type response actions * update docs with actions and custom types metadata API reference * update actions python tests as per #f8e1330 Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com> Co-authored-by: Aravind Shankar <face11301@gmail.com> Co-authored-by: Rakesh Emmadi <12475069+rakeshkky@users.noreply.github.com>
2020-02-13 20:38:23 +03:00
, Hasura.RQL.Types.Action
Add support for GraphQL enum types via enum table references These changes also add a new type, PGColumnType, between PGColInfo and PGScalarType, and they process PGRawColumnType values into PGColumnType values during schema cache generation.
2019-07-22 15:47:13 +03:00
, Hasura.RQL.Types.RemoteSchema
support computed fields returning scalars or set of tables (close #1387) (#2917)
2019-10-18 11:29:47 +03:00
, Hasura.RQL.DDL.ComputedField
, Hasura.RQL.DDL.Relationship
allow custom mutations through actions (#3042) * basic doc for actions * custom_types, sync and async actions * switch to graphql-parser-hs on github * update docs * metadata import/export * webhook calls are now supported * relationships in sync actions * initialise.sql is now in sync with the migration file * fix metadata tests * allow specifying arguments of actions * fix blacklist check on check_build_worthiness job * track custom_types and actions related tables * handlers are now triggered on async actions * default to pgjson unless a field is involved in relationships, for generating definition list * use 'true' for action filter for non admin role * fix create_action_permission sql query * drop permissions when dropping an action * add a hdb_role view (and relationships) to fetch all roles in the system * rename 'webhook' key in action definition to 'handler' * allow templating actions wehook URLs with env vars * add 'update_action' /v1/query type * allow forwarding client headers by setting `forward_client_headers` in action definition * add 'headers' configuration in action definition * handle webhook error response based on status codes * support array relationships for custom types * implement single row mutation, see https://github.com/hasura/graphql-engine/issues/3731 * single row mutation: rename 'pk_columns' -> 'columns' and no-op refactor * use top level primary key inputs for delete_by_pk & account select permissions for single row mutations * use only REST semantics to resolve the webhook response * use 'pk_columns' instead of 'columns' for update_by_pk input * add python basic tests for single row mutations * add action context (name) in webhook payload * Async action response is accessible for non admin roles only if the request session vars equals to action's * clean nulls, empty arrays for actions, custom types in export metadata * async action mutation returns only the UUID of the action * unit tests for URL template parser * Basic sync actions python tests * fix output in async query & add async tests * add admin secret header in async actions python test * document async action architecture in Resolve/Action.hs file * support actions returning array of objects * tests for list type response actions * update docs with actions and custom types metadata API reference * update actions python tests as per #f8e1330 Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com> Co-authored-by: Aravind Shankar <face11301@gmail.com> Co-authored-by: Rakesh Emmadi <12475069+rakeshkky@users.noreply.github.com>
2020-02-13 20:38:23 +03:00
, Hasura.RQL.Types.CustomTypes
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.DDL.Deps
, Hasura.RQL.DDL.Permission.Internal
, Hasura.RQL.DDL.Permission
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
Refactor non-table functions out of Hasura.RQL.DDL.Table
2019-08-14 02:34:37 +03:00
, Hasura.RQL.DDL.Schema.Cache
Split up Hasura.RQL.DDL.Schema.Cache This should hopefully improve compile times by avoiding the need to specialize everything at once.
2019-12-09 01:17:39 +03:00
, Hasura.RQL.DDL.Schema.Cache.Common
, Hasura.RQL.DDL.Schema.Cache.Dependencies
, Hasura.RQL.DDL.Schema.Cache.Fields
, Hasura.RQL.DDL.Schema.Cache.Permission
Refactor non-table functions out of Hasura.RQL.DDL.Table
2019-08-14 02:34:37 +03:00
, Hasura.RQL.DDL.Schema.Catalog
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.RQL.DDL.Schema.Diff
Refactor non-table functions out of Hasura.RQL.DDL.Table
2019-08-14 02:34:37 +03:00
, Hasura.RQL.DDL.Schema.Enum
Add support for GraphQL enum types via enum table references These changes also add a new type, PGColumnType, between PGColInfo and PGScalarType, and they process PGRawColumnType values into PGColumnType values during schema cache generation.
2019-07-22 15:47:13 +03:00
, Hasura.RQL.DDL.Schema.Function
, Hasura.RQL.DDL.Schema.Rename
, Hasura.RQL.DDL.Schema.Table
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, 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
allow custom mutations through actions (#3042) * basic doc for actions * custom_types, sync and async actions * switch to graphql-parser-hs on github * update docs * metadata import/export * webhook calls are now supported * relationships in sync actions * initialise.sql is now in sync with the migration file * fix metadata tests * allow specifying arguments of actions * fix blacklist check on check_build_worthiness job * track custom_types and actions related tables * handlers are now triggered on async actions * default to pgjson unless a field is involved in relationships, for generating definition list * use 'true' for action filter for non admin role * fix create_action_permission sql query * drop permissions when dropping an action * add a hdb_role view (and relationships) to fetch all roles in the system * rename 'webhook' key in action definition to 'handler' * allow templating actions wehook URLs with env vars * add 'update_action' /v1/query type * allow forwarding client headers by setting `forward_client_headers` in action definition * add 'headers' configuration in action definition * handle webhook error response based on status codes * support array relationships for custom types * implement single row mutation, see https://github.com/hasura/graphql-engine/issues/3731 * single row mutation: rename 'pk_columns' -> 'columns' and no-op refactor * use top level primary key inputs for delete_by_pk & account select permissions for single row mutations * use only REST semantics to resolve the webhook response * use 'pk_columns' instead of 'columns' for update_by_pk input * add python basic tests for single row mutations * add action context (name) in webhook payload * Async action response is accessible for non admin roles only if the request session vars equals to action's * clean nulls, empty arrays for actions, custom types in export metadata * async action mutation returns only the UUID of the action * unit tests for URL template parser * Basic sync actions python tests * fix output in async query & add async tests * add admin secret header in async actions python test * document async action architecture in Resolve/Action.hs file * support actions returning array of objects * tests for list type response actions * update docs with actions and custom types metadata API reference * update actions python tests as per #f8e1330 Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com> Co-authored-by: Aravind Shankar <face11301@gmail.com> Co-authored-by: Rakesh Emmadi <12475069+rakeshkky@users.noreply.github.com>
2020-02-13 20:38:23 +03:00
, Hasura.RQL.DDL.Action
, Hasura.RQL.DDL.CustomTypes
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.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
refactor schema.hs into multiple modules (#2661) Mostly moving around things across modules. No change in functionality.
2019-08-09 12:19:17 +03:00
, Hasura.GraphQL.Schema.BoolExp
, Hasura.GraphQL.Schema.Common
allow custom mutations through actions (#3042) * basic doc for actions * custom_types, sync and async actions * switch to graphql-parser-hs on github * update docs * metadata import/export * webhook calls are now supported * relationships in sync actions * initialise.sql is now in sync with the migration file * fix metadata tests * allow specifying arguments of actions * fix blacklist check on check_build_worthiness job * track custom_types and actions related tables * handlers are now triggered on async actions * default to pgjson unless a field is involved in relationships, for generating definition list * use 'true' for action filter for non admin role * fix create_action_permission sql query * drop permissions when dropping an action * add a hdb_role view (and relationships) to fetch all roles in the system * rename 'webhook' key in action definition to 'handler' * allow templating actions wehook URLs with env vars * add 'update_action' /v1/query type * allow forwarding client headers by setting `forward_client_headers` in action definition * add 'headers' configuration in action definition * handle webhook error response based on status codes * support array relationships for custom types * implement single row mutation, see https://github.com/hasura/graphql-engine/issues/3731 * single row mutation: rename 'pk_columns' -> 'columns' and no-op refactor * use top level primary key inputs for delete_by_pk & account select permissions for single row mutations * use only REST semantics to resolve the webhook response * use 'pk_columns' instead of 'columns' for update_by_pk input * add python basic tests for single row mutations * add action context (name) in webhook payload * Async action response is accessible for non admin roles only if the request session vars equals to action's * clean nulls, empty arrays for actions, custom types in export metadata * async action mutation returns only the UUID of the action * unit tests for URL template parser * Basic sync actions python tests * fix output in async query & add async tests * add admin secret header in async actions python test * document async action architecture in Resolve/Action.hs file * support actions returning array of objects * tests for list type response actions * update docs with actions and custom types metadata API reference * update actions python tests as per #f8e1330 Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com> Co-authored-by: Aravind Shankar <face11301@gmail.com> Co-authored-by: Rakesh Emmadi <12475069+rakeshkky@users.noreply.github.com>
2020-02-13 20:38:23 +03:00
, Hasura.GraphQL.Schema.CustomTypes
, Hasura.GraphQL.Schema.Builder
, Hasura.GraphQL.Schema.Action
refactor schema.hs into multiple modules (#2661) Mostly moving around things across modules. No change in functionality.
2019-08-09 12:19:17 +03:00
, Hasura.GraphQL.Schema.Function
, Hasura.GraphQL.Schema.OrderBy
, Hasura.GraphQL.Schema.Select
, Hasura.GraphQL.Schema.Merge
, Hasura.GraphQL.Schema.Mutation.Common
, Hasura.GraphQL.Schema.Mutation.Insert
, Hasura.GraphQL.Schema.Mutation.Update
, Hasura.GraphQL.Schema.Mutation.Delete
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
Multiplex all subscriptions, grouping them by their resolved SQL query
2019-08-28 15:19:21 +03:00
, Hasura.GraphQL.Execute.LiveQuery.Options
, Hasura.GraphQL.Execute.LiveQuery.Plan
, Hasura.GraphQL.Execute.LiveQuery.Poll
, Hasura.GraphQL.Execute.LiveQuery.State
, Hasura.GraphQL.Execute.LiveQuery.TMap
refactor graphql query execution logic (#1855)
2019-03-25 21:25:25 +03:00
, Hasura.GraphQL.Resolve
allow custom mutations through actions (#3042) * basic doc for actions * custom_types, sync and async actions * switch to graphql-parser-hs on github * update docs * metadata import/export * webhook calls are now supported * relationships in sync actions * initialise.sql is now in sync with the migration file * fix metadata tests * allow specifying arguments of actions * fix blacklist check on check_build_worthiness job * track custom_types and actions related tables * handlers are now triggered on async actions * default to pgjson unless a field is involved in relationships, for generating definition list * use 'true' for action filter for non admin role * fix create_action_permission sql query * drop permissions when dropping an action * add a hdb_role view (and relationships) to fetch all roles in the system * rename 'webhook' key in action definition to 'handler' * allow templating actions wehook URLs with env vars * add 'update_action' /v1/query type * allow forwarding client headers by setting `forward_client_headers` in action definition * add 'headers' configuration in action definition * handle webhook error response based on status codes * support array relationships for custom types * implement single row mutation, see https://github.com/hasura/graphql-engine/issues/3731 * single row mutation: rename 'pk_columns' -> 'columns' and no-op refactor * use top level primary key inputs for delete_by_pk & account select permissions for single row mutations * use only REST semantics to resolve the webhook response * use 'pk_columns' instead of 'columns' for update_by_pk input * add python basic tests for single row mutations * add action context (name) in webhook payload * Async action response is accessible for non admin roles only if the request session vars equals to action's * clean nulls, empty arrays for actions, custom types in export metadata * async action mutation returns only the UUID of the action * unit tests for URL template parser * Basic sync actions python tests * fix output in async query & add async tests * add admin secret header in async actions python test * document async action architecture in Resolve/Action.hs file * support actions returning array of objects * tests for list type response actions * update docs with actions and custom types metadata API reference * update actions python tests as per #f8e1330 Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com> Co-authored-by: Aravind Shankar <face11301@gmail.com> Co-authored-by: Rakesh Emmadi <12475069+rakeshkky@users.noreply.github.com>
2020-02-13 20:38:23 +03:00
, Hasura.GraphQL.Resolve.Action
refactor schema.hs into multiple modules (#2661) Mostly moving around things across modules. No change in functionality.
2019-08-09 12:19:17 +03:00
, Hasura.GraphQL.Resolve.Types
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.GraphQL.Resolve.Context
refactor schema.hs into multiple modules (#2661) Mostly moving around things across modules. No change in functionality.
2019-08-09 12:19:17 +03:00
, Hasura.GraphQL.Resolve.BoolExp
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, 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
breaking: server logging changes (close #507, close #2171) (#1835)
2019-07-11 08:37:06 +03:00
, Hasura.GraphQL.Logging
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
Multiplex all subscriptions, grouping them by their resolved SQL query
2019-08-28 15:19:21 +03:00
, Control.Concurrent.Extended
Add support for GraphQL enum types via enum table references These changes also add a new type, PGColumnType, between PGColInfo and PGScalarType, and they process PGRawColumnType values into PGColumnType values during schema cache generation.
2019-07-22 15:47:13 +03:00
, Control.Lens.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
allow custom mutations through actions (#3042) * basic doc for actions * custom_types, sync and async actions * switch to graphql-parser-hs on github * update docs * metadata import/export * webhook calls are now supported * relationships in sync actions * initialise.sql is now in sync with the migration file * fix metadata tests * allow specifying arguments of actions * fix blacklist check on check_build_worthiness job * track custom_types and actions related tables * handlers are now triggered on async actions * default to pgjson unless a field is involved in relationships, for generating definition list * use 'true' for action filter for non admin role * fix create_action_permission sql query * drop permissions when dropping an action * add a hdb_role view (and relationships) to fetch all roles in the system * rename 'webhook' key in action definition to 'handler' * allow templating actions wehook URLs with env vars * add 'update_action' /v1/query type * allow forwarding client headers by setting `forward_client_headers` in action definition * add 'headers' configuration in action definition * handle webhook error response based on status codes * support array relationships for custom types * implement single row mutation, see https://github.com/hasura/graphql-engine/issues/3731 * single row mutation: rename 'pk_columns' -> 'columns' and no-op refactor * use top level primary key inputs for delete_by_pk & account select permissions for single row mutations * use only REST semantics to resolve the webhook response * use 'pk_columns' instead of 'columns' for update_by_pk input * add python basic tests for single row mutations * add action context (name) in webhook payload * Async action response is accessible for non admin roles only if the request session vars equals to action's * clean nulls, empty arrays for actions, custom types in export metadata * async action mutation returns only the UUID of the action * unit tests for URL template parser * Basic sync actions python tests * fix output in async query & add async tests * add admin secret header in async actions python test * document async action architecture in Resolve/Action.hs file * support actions returning array of objects * tests for list type response actions * update docs with actions and custom types metadata API reference * update actions python tests as per #f8e1330 Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com> Co-authored-by: Aravind Shankar <face11301@gmail.com> Co-authored-by: Rakesh Emmadi <12475069+rakeshkky@users.noreply.github.com>
2020-02-13 20:38:23 +03:00
, Data.List.Extended
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
, Data.HashMap.Strict.Extended
server: use insert-ordered-containers for ordered map
2018-06-28 11:19:27 +03:00
, Data.HashMap.Strict.InsOrd.Extended
Multiplex all subscriptions, grouping them by their resolved SQL query
2019-08-28 15:19:21 +03:00
, Data.Sequence.NonEmpty
, Data.TByteString
, Data.Text.Extended
server: add support for webhook connection expiration (#4196) * add expiry time to webhook user info This also adds an optional message to webhook errors: if we fail to parse an expiry time, we will log a warning with the parse error. * refactored Auth This change had one main goal: put in common all expiry time extraction code between the JWT and WebHook parts of the code. Furthermore, this change also moves all WebHook specific code to its own module, similarly to what is done for JWT. * Remove dependency on string-conversions in favor of text-conversions string-conversions silently uses UTF8 instead of being explicit about it, and it uses lenientDecode when decoding ByteStrings when it’s usually better to reject invalid UTF8 input outright. text-conversions solves both those problems. Co-authored-by: Alexis King <lexi.lambda@gmail.com>
2020-04-03 03:00:13 +03:00
, Data.Parser.Expires
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.SQL.DML
Add support for GraphQL enum types via enum table references These changes also add a new type, PGColumnType, between PGColInfo and PGScalarType, and they process PGRawColumnType values into PGColumnType values during schema cache generation.
2019-07-22 15:47:13 +03:00
, Hasura.SQL.Error
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
, Hasura.SQL.GeoJSON
workaround postgres default limit of 63 chars for identifiers (close #688) (#707)
2018-10-12 12:28:43 +03:00
, Hasura.SQL.Rewrite
Add support for GraphQL enum types via enum table references These changes also add a new type, PGColumnType, between PGColInfo and PGScalarType, and they process PGRawColumnType values into PGColumnType values during schema cache generation.
2019-07-22 15:47:13 +03:00
, Hasura.SQL.Time
, Hasura.SQL.Types
, Hasura.SQL.Value
adds basic support for remote schemas/schema stitching (#952)
2018-11-23 16:02:46 +03:00
, Network.URI.Extended
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
executable graphql-engine
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
import: common-all, common-exe
move raven into graphql-engine repo
2018-06-27 16:11:32 +03:00
hs-source-dirs: src-exec
server: Parameterize the graphql-engine library over the version (#3668)
2020-01-23 00:55:55 +03:00
main-is: Main.hs
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
build-depends: base
, graphql-engine
server: Parameterize the graphql-engine library over the version (#3668)
2020-01-23 00:55:55 +03:00
, bytestring
refactor some internal components (#3414)
2019-11-26 15:14:21 +03:00
, pg-client
, text
server: Parameterize the graphql-engine library over the version (#3668)
2020-01-23 00:55:55 +03:00
, text-conversions
check for updates every 24 hrs in background (fix #204) (#209)
2018-07-27 12:34:50 +03:00
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
test-suite graphql-engine-tests
import: common-all, common-exe
type: exitcode-stdio-1.0
build-depends:
Add Hasura.Incremental, a library for incremental builds
2019-11-18 21:45:54 +03:00
, aeson
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
, base
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
, bytestring
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
, graphql-engine
Use arrows instead of monads to define the schema cache construction
2019-11-27 01:49:42 +03:00
, hspec >=2.6.1 && <3
, hspec-core >=2.6.1 && <3
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
, hspec-expectations-lifted
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
, http-client
, http-client-tls
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
, lifted-base
, monad-control
Add Hasura.Incremental, a library for incremental builds
2019-11-18 21:45:54 +03:00
, mtl
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
, natural-transformation >=0.4 && <0.5
save permissions, relationships and collections in catalog with 'is_system_defined' explicitly (#3165) * save permissions, relationships and collections in catalog with 'is_system_defined' * Use common stanzas in the .cabal file * Refactor migration code into lib instead of exe * Add new server test suite that exercises migrations * Make graphql-engine clean succeed even if the schema does not exist
2019-10-21 19:01:05 +03:00
, optparse-applicative
, pg-client
Add downgrade command (close #1156) (#3760) * Add downgrade command * Add docs per @lexi-lambda's suggestions * make tests pass * Update hdb_version once, from Haskell * more work based on feedback * Improve the usage message * Small docs changes * Test downgrades exist for each tag * Update downgrading.rst * Use git-log to find tags which are ancestors of the current commit Co-authored-by: Vamshi Surabhi <0x777@users.noreply.github.com>
2020-02-07 14:03:12 +03:00
, process
Initial benchmarks for caching. Closes #3530 These aren't suitable e.g. for running in CI since some take far too long (and an impossibly long-time when running under criterion's normal bootstrapping sampling regime. We might try to improve this ourselves: https://github.com/bos/criterion/issues/218 An initial summary analysis will be in #3530.
2019-12-13 22:52:19 +03:00
, QuickCheck
Add downgrade command (close #1156) (#3760) * Add downgrade command * Add docs per @lexi-lambda's suggestions * make tests pass * Update hdb_version once, from Haskell * more work based on feedback * Improve the usage message * Small docs changes * Test downgrades exist for each tag * Update downgrading.rst * Use git-log to find tags which are ancestors of the current commit Co-authored-by: Vamshi Surabhi <0x777@users.noreply.github.com>
2020-02-07 14:03:12 +03:00
, safe
, split
Add Hasura.Incremental, a library for incremental builds
2019-11-18 21:45:54 +03:00
, time
Refactor schema cache construction to avoid imperative updates wip: fix error codes in remote schema tests
2019-11-20 21:21:30 +03:00
, transformers-base
Add Hasura.Incremental, a library for incremental builds
2019-11-18 21:45:54 +03:00
, unordered-containers
accept a new argument `claims_namespace_path` in JWT config (#4365) * add new optional field `claims_namespace_path` in JWT config * return value when empty array is found in executeJSONPath * update the docs related to claims_namespace_path * improve encodeJSONPath, add property tests for parseJSONPath * throw error if both claims_namespace_path and claims_namespace are set * refactor the Data.Parser.JsonPath to Data.Parser.JSONPathSpec * update the JWT docs Co-Authored-By: Marion Schleifer <marion@hasura.io> Co-authored-by: Marion Schleifer <marion@hasura.io> Co-authored-by: rakeshkky <12475069+rakeshkky@users.noreply.github.com> Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com>
2020-04-16 09:45:21 +03:00
, text
Add Hasura.Incremental, a library for incremental builds
2019-11-18 21:45:54 +03:00
hs-source-dirs: src-test
main-is: Main.hs
other-modules:
fix cache-control header parsing for JWK (fix #3655) (#3676) write a proper parser according to the RFC https://tools.ietf.org/html/rfc7234#section-5.2
2020-01-14 00:56:51 +03:00
Data.Parser.CacheControlSpec
allow custom mutations through actions (#3042) * basic doc for actions * custom_types, sync and async actions * switch to graphql-parser-hs on github * update docs * metadata import/export * webhook calls are now supported * relationships in sync actions * initialise.sql is now in sync with the migration file * fix metadata tests * allow specifying arguments of actions * fix blacklist check on check_build_worthiness job * track custom_types and actions related tables * handlers are now triggered on async actions * default to pgjson unless a field is involved in relationships, for generating definition list * use 'true' for action filter for non admin role * fix create_action_permission sql query * drop permissions when dropping an action * add a hdb_role view (and relationships) to fetch all roles in the system * rename 'webhook' key in action definition to 'handler' * allow templating actions wehook URLs with env vars * add 'update_action' /v1/query type * allow forwarding client headers by setting `forward_client_headers` in action definition * add 'headers' configuration in action definition * handle webhook error response based on status codes * support array relationships for custom types * implement single row mutation, see https://github.com/hasura/graphql-engine/issues/3731 * single row mutation: rename 'pk_columns' -> 'columns' and no-op refactor * use top level primary key inputs for delete_by_pk & account select permissions for single row mutations * use only REST semantics to resolve the webhook response * use 'pk_columns' instead of 'columns' for update_by_pk input * add python basic tests for single row mutations * add action context (name) in webhook payload * Async action response is accessible for non admin roles only if the request session vars equals to action's * clean nulls, empty arrays for actions, custom types in export metadata * async action mutation returns only the UUID of the action * unit tests for URL template parser * Basic sync actions python tests * fix output in async query & add async tests * add admin secret header in async actions python test * document async action architecture in Resolve/Action.hs file * support actions returning array of objects * tests for list type response actions * update docs with actions and custom types metadata API reference * update actions python tests as per #f8e1330 Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com> Co-authored-by: Aravind Shankar <face11301@gmail.com> Co-authored-by: Rakesh Emmadi <12475069+rakeshkky@users.noreply.github.com>
2020-02-13 20:38:23 +03:00
Data.Parser.URLTemplate
accept a new argument `claims_namespace_path` in JWT config (#4365) * add new optional field `claims_namespace_path` in JWT config * return value when empty array is found in executeJSONPath * update the docs related to claims_namespace_path * improve encodeJSONPath, add property tests for parseJSONPath * throw error if both claims_namespace_path and claims_namespace are set * refactor the Data.Parser.JsonPath to Data.Parser.JSONPathSpec * update the JWT docs Co-Authored-By: Marion Schleifer <marion@hasura.io> Co-authored-by: Marion Schleifer <marion@hasura.io> Co-authored-by: rakeshkky <12475069+rakeshkky@users.noreply.github.com> Co-authored-by: Tirumarai Selvan <tirumarai.selvan@gmail.com>
2020-04-16 09:45:21 +03:00
Data.Parser.JSONPathSpec
Add request timings and count histograms to telemetry. Closes #3552 We upload a set of accumulating timers and counters to track service time for different types of operations, across several dimensions (e.g. did we hit the plan cache, was a remote involved, etc.) Also... Standardize on DiffTime as a standard duration type, and try to use it consistently. See discussion here: https://github.com/hasura/graphql-engine/pull/3584#pullrequestreview-340679369 It should be possible to overwrite that module so the new threadDelay sticks per the pattern in #3705 blocked on #3558 Rename the Control.Concurrent.Extended.threadDelay to `sleep` since a naive use with a literal argument would be very bad! We catch a bug in 'computeTimeDiff'. Add convenient 'Read' instances to the time unit utility types. Make 'Second' a newtype to support this.
2020-01-16 04:56:57 +03:00
Data.TimeSpec
Add Hasura.Incremental, a library for incremental builds
2019-11-18 21:45:54 +03:00
Hasura.IncrementalSpec
Hasura.RQL.MetadataSpec
Hasura.Server.MigrateSpec
Add request timings and count histograms to telemetry. Closes #3552 We upload a set of accumulating timers and counters to track service time for different types of operations, across several dimensions (e.g. did we hit the plan cache, was a remote involved, etc.) Also... Standardize on DiffTime as a standard duration type, and try to use it consistently. See discussion here: https://github.com/hasura/graphql-engine/pull/3584#pullrequestreview-340679369 It should be possible to overwrite that module so the new threadDelay sticks per the pattern in #3705 blocked on #3558 Rename the Control.Concurrent.Extended.threadDelay to `sleep` since a naive use with a literal argument would be very bad! We catch a bug in 'computeTimeDiff'. Add convenient 'Read' instances to the time unit utility types. Make 'Second' a newtype to support this.
2020-01-16 04:56:57 +03:00
Hasura.Server.TelemetrySpec
Initial benchmarks for caching. Closes #3530 These aren't suitable e.g. for running in CI since some take far too long (and an impossibly long-time when running under criterion's normal bootstrapping sampling regime. We might try to improve this ourselves: https://github.com/bos/criterion/issues/218 An initial summary analysis will be in #3530.
2019-12-13 22:52:19 +03:00
-- Benchmarks related to caching (e.g. the plan cache).
--
-- NOTE: Some of these are very slow and can only be reasonably run with `cache -n 1` for now.
benchmark cache
import: common-all, common-exe
type: exitcode-stdio-1.0
main-is: Main.hs
hs-source-dirs: src-bench-cache
build-depends: base
, criterion
, mwc-random
, mwc-probability
, vector
, deepseq
, graphql-engine
, split
, async
, text
, bytestring
Reference in New Issue Copy Permalink