3d5fb984b0
## Description There is a bug in the metadata defaults code, see [the original PR](https://github.com/hasura/graphql-engine-mono/pull/6286). Steps to reproduce this issue: * Start a new HGE project * Start HGE with a defaults argument: `HASURA_GRAPHQL_LOG_LEVEL=debug cabal run exe:graphql-engine -- serve --enable-console --console-assets-dir=./console/static/dist --metadata-defaults='{"backend_configs": {"dataconnector": {"mongo": {"display_name": "BONGOBB", "uri": "http://localhost:8123"}}}}'` * Add a source (doesn't need to be related to the defaults) * Export metadata * See that the defaults are present in the exported metadata ## Related Issues * Github Issue: https://github.com/hasura/graphql-engine/issues/9237 * Jira: https://hasurahq.atlassian.net/browse/GDC-647 * Original PR: https://github.com/hasura/graphql-engine-mono/pull/6286 ## Solution * The test for if defaults should be included for metadata api operations has been extended to check for updates * Metadata inconsistencies have been hidden for `/capabilities` calls on startup ## TODO * [x] Fix bug * [x] Write tests * [x] OSS Metadata Migration to correct persisted data - `server/src-rsr/migrations/47_to_48.sql` * [x] Cloud Metadata Migration - `pro/server/res/cloud/migrations/6_to_7.sql` * [x] Bump Catalog Version - `server/src-rsr/catalog_version.txt` * [x] Update Catalog Versions - `server/src-rsr/catalog_versions.txt` (This will be done by Infra when creating a release) * [x] Log connection error as it occurs *(Already being logged. Requires `--enabled-log-types startup,webhook-log,websocket-log,http-log,data-connector-log`) * [x] Don't mark metadata inconsistencies for this call. ## Questions * [ ] Does the `pro/server/res/cloud/migrations/6_to_7.sql` cover the cloud scenarios? * [ ] Should we have `SET search_path` in migrations? * [x] What should be in `server/src-rsr/catalog_versions.txt`? ## Testing To test the solution locally run: > docker compose up -d and > cabal run -- exe:api-tests --skip BigQuery --skip SQLServer --skip '/Test.API.Explain/Postgres/' ## Solution In `runMetadataQuery` in `server/src-lib/Hasura/Server/API/Metadata.hs`: ```diff - if (exportsMetadata _rqlMetadata) + if (exportsMetadata _rqlMetadata || queryModifiesMetadata _rqlMetadata) ``` This ensures that defaults aren't present in operations that serialise metadata. Note: You might think that `X_add_source` would need the defaults to be present to add a source that references the defaults, but since the resolution occurs in the schema-cache building phase, the defaults can be excluded for the metadata modifications required for `X_add_source`. In addition to the code-change, a metadata migration has been introduced in order to clean up serialised defaults. The following scenarios need to be considered for both OSS and Cloud: * The user has not had defaults serialised * The user has had the defaults serialised and no other backends configured * The user has had the defaults serialised and has also configured other backends We want to remove as much of the metadata as possible without any user-specified data and this should be reflected in migration `server/src-rsr/migrations/47_to_48.sql`. ## Server checklist ### Catalog upgrade Does this PR change Hasura Catalog version? - ✅ Yes ### Metadata Does this PR add a new Metadata feature? - ✅ No ### GraphQL - ✅ No new GraphQL schema is generated ### Breaking changes - ✅ No Breaking changes ## Changelog __Component__ : server __Type__: bugfix __Product__: community-edition ### Short Changelog Fixes a metadata defaults serialization bug and introduces a metadata migration to correct data that has been persisted due to the bug. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7034 GitOrigin-RevId: ad7d4f748397a1a607f2c0c886bf0fbbc3f873f2 |
||
|---|---|---|
| .circleci | ||
| .github | ||
| architecture | ||
| assets | ||
| cabal | ||
| cli | ||
| cli-ext | ||
| community | ||
| console | ||
| contrib/metadata-types | ||
| dc-agents | ||
| docker-compose | ||
| docs | ||
| frontend | ||
| install-manifests | ||
| nix | ||
| packaging | ||
| rfcs | ||
| scripts | ||
| server | ||
| translations | ||
| .dockerignore | ||
| .envrc | ||
| .envrc.local.example | ||
| .ghcversion | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .hlint.yaml | ||
| .kodiak.toml | ||
| .nvmrc | ||
| .prettierignore | ||
| cabal.project | ||
| cabal.project.freeze | ||
| CHANGELOG.md | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| docker-compose.yaml | ||
| event-triggers.md | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE | ||
| LICENSE-community | ||
| Makefile | ||
| package-lock.json | ||
| README.md | ||
| remote-schemas.md | ||
| sample.hie.yaml | ||
| SECURITY.md | ||
| shell.nix | ||
| weeder.dhall | ||
Hasura GraphQL Engine
Hasura is an open-source product that accelerates API development by 10x by giving you GraphQL or REST APIs with built-in authorization on your data, instantly.
Read more at hasura.io and the docs.
Features
- Make powerful queries: Built-in filtering, pagination, pattern search, bulk insert, update, delete mutations
- Works with existing, live databases: Point it to an existing database to instantly get a ready-to-use GraphQL API
- Realtime: Convert any GraphQL query to a live query by using subscriptions
- Merge remote schemas: Access custom GraphQL schemas for business logic via a single GraphQL Engine endpoint. Read more.
- Extend with Actions: Write REST APIs to extend Hasura’s schema with custom business logic.
- Trigger webhooks or serverless functions: On Postgres insert/update/delete events (read more)
- Scheduled Triggers: Execute custom business logic at specific points in time using a cron config or a one-off event.
- Fine-grained access control: Dynamic access control that integrates with your auth system (eg: auth0, firebase-auth)
- Admin UI & Migrations: Admin UI & Rails-inspired schema migrations
- Supported Databases: Supports PostgreSQL (and its flavors), MS SQL Server and Big Query. Support for more databases coming soon.
Read more at hasura.io and the docs.
Table of contents
Table of Contents
- Quickstart:
- Architecture
- Client-side tooling
- Add business logic
- Demos
- Support & Troubleshooting
- Stay up to date
- Contributing
- Brand assets
- License
- Translations
Quickstart:
One-click deployment on Hasura Cloud
The fastest and easiest way to try Hasura out is via Hasura Cloud.
-
Click on the following button to deploy GraphQL engine on Hasura Cloud including Postgres add-on or using an existing Postgres database:
-
Open the Hasura console
Click on the button "Launch console" to open the Hasura console.
-
Make your first GraphQL query
Create a table and instantly run your first query. Follow this simple guide.
Other one-click deployment options
Check out the instructions for the following one-click deployment options:
| Infra provider | One-click link | Additional information |
|---|---|---|
| Heroku |  |
docs |
| DigitalOcean |  |
docs |
| Azure |  |
docs |
| Render |  |
docs |
Other deployment methods
For Docker-based deployment and advanced configuration options, see deployment guides or install manifests.
Architecture
The Hasura GraphQL Engine fronts a Postgres database instance and can accept GraphQL requests from your client apps. It can be configured to work with your existing auth system and can handle access control using field-level rules with dynamic variables from your auth system.
You can also merge remote GraphQL schemas and provide a unified GraphQL API.
Client-side tooling
Hasura works with any GraphQL client. See awesome-graphql for a list of clients. Our frontend tutorial series also have integrations with GraphQL clients for different frameworks.
Add business logic
GraphQL Engine provides easy-to-reason, scalable and performant methods for adding custom business logic to your backend:
Remote schemas
Add custom resolvers in a remote schema in addition to Hasura's database-based GraphQL schema. Ideal for use-cases like implementing a payment API, or querying data that is not in your database - read more.
Actions
Actions are a way to extend Hasura’s schema with custom business logic using custom queries and mutations. Actions can be added to Hasura to handle various use cases such as data validation, data enrichment from external sources and any other complex business logic - read more
Trigger webhooks on database events
Add asynchronous business logic that is triggered based on database events. Ideal for notifications, data-pipelines from Postgres or asynchronous processing - read more.
Derived data or data transformations
Transform data in Postgres or run business logic on it to derive another dataset that can be queried using GraphQL Engine - read more.
Demos
Check out all the example applications in the community/sample-apps directory.
Realtime applications
-
Group Chat application built with React, includes a typing indicator, online users & new message notifications.
-
Live location tracking app that shows a running vehicle changing the current GPS coordinates moving on a map.
-
A real-time dashboard for data aggregations on continuously changing data.
Videos
- Add GraphQL to a self-hosted GitLab instance (3:44 mins)
- Todo app with Auth0 and GraphQL backend (4:00 mins)
- GraphQL on GitLab integrated with GitLab auth (4:05 mins)
- Dashboard for 10million rides with geo-location (PostGIS, Timescale) (3:06 mins)
Support & Troubleshooting
The documentation and community will help you troubleshoot most issues. If you have encountered a bug or need to get in touch with us, you can contact us using one of the following channels:
- Support & feedback: Discord
- Issue & bug tracking: GitHub issues
- Follow product updates: @HasuraHQ
- Talk to us on our website chat
We are committed to fostering an open and welcoming environment in the community. Please see the Code of Conduct.
If you want to report a security issue, please read this.
Stay up to date
We release new features every month. Sign up for our newsletter by using the link below. We send newsletters only once a month. https://hasura.io/newsletter/
Contributing
Check out our contributing guide for more details.
Brand assets
Hasura brand assets (logos, the Hasura mascot, powered by badges etc.) can be found in the assets/brand folder. Feel free to use them in your application/website etc. We'd be thrilled if you add the "Powered by Hasura" badge to your applications built using Hasura. ❤️
<!-- For light backgrounds -->
<a href="https://hasura.io">
<img width="150px" src="https://graphql-engine-cdn.hasura.io/img/powered_by_hasura_primary_darkbg.svg" />
</a>
<!-- For dark backgrounds -->
<a href="https://hasura.io">
<img width="150px" src="https://graphql-engine-cdn.hasura.io/img/powered_by_hasura_primary_lightbg.svg" />
</a>
License
The core GraphQL Engine is available under the Apache License 2.0 (Apache-2.0).
All other contents (except those in server, cli and
console directories) are available under the MIT License.
This includes everything in the docs and community
directories.
Translations
This readme is available in the following translations:
- Japanese 🇯🇵 (🙏 @moksahero)
- French 🇫🇷 (🙏 @l0ck3)
- Bosnian 🇧🇦 (🙏 @hajro92)
- Russian 🇷🇺 (🙏 @highflyer910)
- Greek 🇬🇷 (🙏 @MIP2000)
- Spanish 🇲🇽(🙏 @ferdox2)
- Indonesian 🇮🇩 (🙏 @anwari666)
- Brazilian Portuguese 🇧🇷 (🙏 @rubensmp)
- German 🇩🇪 (🙏 @FynnGrandke)
- Chinese 🇨🇳 (🙏 @jagreetdg & @johnbanq)
- Turkish 🇹🇷 (🙏 @berat)
- Korean 🇰🇷 (🙏 @라스크)
- Italian 🇮🇹 (🙏 @befire)
Translations for other files can be found here.