hasura / hasura/graphql-engine

Can't make changes to permissions when schema changes via console is disabled

Open
#8,258 0 comments 0 reactions 0 assignees View on GitHub
c/console k/bug support/needs-more-info
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version: 2.2.1 & 2.2.0
CLI Version (for CLI related issue): 2.2.0

### Environment

OSS

### What is the expected behaviour?

Just upgraded from v1 Hasura to v2. Had schema changes via console disabled. For some reason, in v2 I can no longer update role permissions along with any other metadata related functions. Enabling "Allow Postgres schema changes via console" suddenly makes it all work again.

If it's disabled, and I try to do any changes I get the following error:
![image](https://user-images.githubusercontent.com/7835503/155940739-a4ea4d1c-88ad-4022-a643-21489aceb22a.png)

Once "Allow Postgres schema changes via console" is enabled, it starts working fine again.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the permission and metadata update failure on Hasura v2.2.0 or v2.2.1 with “Allow Postgres schema changes via console” disabled, then compare it with the setting enabled. Done means role-permission and other metadata changes work without allowing Postgres schema changes through the console.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres
Domain
authorization, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.