When i have a remote schema which doesn't work (lets say the server is down or deleted), i'm not able to make any postgres schema changes to Hasura GraphQL via console. (this is expected, because of the dependancy check that happens during merging).

But right now to get around this, i have to delete the remote schema which isn't working. If i can enable/disable remote schema, instead of deleting, it would be a better experience during development.
This feature basically helps in preserving the config (url, name and headers) of remote schema.