hasura / hasura/graphql-engine

REST Endpoints don't get applied with other metadata

Open
#7,898 8 comments 8 reactions 0 assignees View on GitHub
c/cli k/bug t/product-platform
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information
INFO hasura cli version=v2.0.9
INFO hasura graphql engine endpoint="http://localhost:8080/" version=v2.0.10

### Environment
Self-hosted

### What is the expected behaviour?
Rest endpoints are loaded from config files

### Keywords
rest endpoint, metadata, migrations

### What is the current behaviour?
Rest endpoints are not loaded from config files

### How to reproduce the issue?

1. Add rest endpoint
2. Recreate database
2. Start server with empty database (let it load metadata from files)

### Any possible solutions?

**rest_endpoints** is not saved to config files as far as I see - need to save it along with other pieces of metadata.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how rest_endpoints is represented in the config files and how metadata is loaded when the server starts with an empty database. Reproduce the listed database recreation and startup sequence, then verify that rest endpoints are saved and loaded alongside the other metadata.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.